TAILIEUCHUNG - Bắt đầu với IBM Websphere smash - p 24

212 Chapter 9 Security Model At this point, our application is ready to serve pages using the HTTPS protocol. Let’s create a simple landing page to verify that our SSL certificate is recognized. Create a new file called /public/, whose contents are shown in Listing . Listing Main Landing Page (/public/) sMash Security Welcome to the Security Application This page is not protected Try going to a "Protected page. Open your browser to https://localhost:8443/ (note the https protocol, and the special port number we defined earlier). You should first get a warning from your browser that the. | 212 Chapter 9 Security Model At this point our application is ready to serve pages using the HTTPS protocol. Let s create a simple landing page to verify that our SSL certificate is recognized. Create a new file called public whose contents are shown in Listing . Listing Main Landing Page public html head title sMash Security title head body h1 Welcome to the Security Application h1 h3 This page is not protected h3 h2 Try going to a a href getRelativeUri my Protected page a . h2 body html Open your browser to https localhost 8443 note the https protocol and the special port number we defined earlier . You should first get a warning from your browser that the connection is untrusted due to using a self-signed certificate. This is a good behavior as it s validating that WebSphere sMash was able to process the certificate and your browser just doesn t approve its validity. Click through the warning to acknowledge this issue and optionally add this as an exception to your browser. You should then be taken to our main landing page as shown in Figure . We ll build on this shortly to add a secured page as well as login and logout pages. That wasn t so bad was it Next let s go over user authentication and how we actually protect various resources in our application. Figure Main landing page Download from SSL Configuration 213 Enabling Security A single setting enables security within a WebSphere sMash application. A secure application by default protects all resources addressable by URL and simply requires users to be authenticated but no other restrictions are applied. We ll walk through fine tuning which resources should be protected and for which users and groups later in this chapter. To enable security add the line shown in Listing . This provides a single location to quickly disable security during debugging by just commenting out this one line regardless of any other security-based configurations

TỪ KHÓA LIÊN QUAN
TAILIEUCHUNG - Chia sẻ tài liệu không giới hạn
Địa chỉ : 444 Hoang Hoa Tham, Hanoi, Viet Nam
Website : tailieuchung.com
Email : tailieuchung20@gmail.com
Tailieuchung.com là thư viện tài liệu trực tuyến, nơi chia sẽ trao đổi hàng triệu tài liệu như luận văn đồ án, sách, giáo trình, đề thi.
Chúng tôi không chịu trách nhiệm liên quan đến các vấn đề bản quyền nội dung tài liệu được thành viên tự nguyện đăng tải lên, nếu phát hiện thấy tài liệu xấu hoặc tài liệu có bản quyền xin hãy email cho chúng tôi.
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.