WAS v8.5 > End-to-end paths

End-to-end paths for security

Subtopics

• Configure LTPA and work with keys
  You must configure Lightweight Third Party Authentication (LTPA) when we set up security for the first time. LTPA is the default authentication mechanism for WebSphere Application Server. After we have configured LTPA we can generate LTPA keys manually or automatically.
• Customize application login with JAAS
  Using JAAS, we can customize the application login.
• Create a single sign-on for HTTP requests using SPNEGO Web authentication
  Creating 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
  You must perform steps in this article in order to set up Kerberos as the authentication mechanism for WAS.

+

Search Tips   |   Advanced Search