Network Deployment (Distributed operating systems), v8.0 > End-to-end paths
End-to-end paths for security
- Configure LTPA and working with keys
Configure Lightweight Third Party Authentication (LTPA) when you set up security for the first time. LTPA is the default authentication mechanism for WAS. After we have configured LTPA you can generate LTPA keys manually or automatically.
- Customize application login with JAAS
Use JAAS, you can customize the application login.
- Create a single sign-on for HTTP requests using SPNEGO Web authentication
Create single sign-ons for HTTP requests using the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) web authentication for WAS requires the performance of several distinct, yet related functions that when completed, allow HTTP users to log in and authenticate to the Microsoft domain controller only once at their desktop and to receive automatic authentication from the WAS.
- Set up Kerberos as the authentication mechanism for WAS
We must perform steps in this article in order to set up Kerberos as the authentication mechanism for WAS.