When the browser sends a GET request to the Distributed Authentication User Interface, the following events occur.
Using the parameters in the GET request, the Distributed Authentication User Interface contacts the Authentication Service installed on the Access Manager Server.
Authentication Service determines the appropriate authentication module to use based upon Access Manager configuration and the request parameters passed by the Distributed Authentication User Interface through the Authentication client APIs.
For example, if Access Manager is configured to use the LDAP Authentication type of module, the Authentication Service determines that the LDAP Authentication login page will be used.
Authentication Service determines which presentation callbacks should be presented, and sends to the Distributed Authentication User Interface all necessary credentials, requirements, and callbacks to be in used the presentation framework layer.
Client Detection Service determines which protocol, such as HTML or WML, to use to display the login page.
The Distributed Authentication User Interface returns to the Web browser a dynamic presentation extraction page along with the session cookie.
The presentation extraction page contains the appropriate credentials request and callbacks info obtained from the Access Manager Server.
The user’s browser displays the login page.
The user enters information in the Username and Password fields of the login page.
The browser replies to the Distributed Authentication User Interface with a POST that contains the required credentials.
The Distributed Authentication User Interface uses the Authentication client APIs to pass credentials to the Access Manager Server.
The Authentication Service uses the appropriate authentication module type to validate the user’s credentials.
For example, if the LDAP authentication module type is used, Authentication Service verifies that the username and password provided exist in the LDAP directory. Other authentication module types have different requirements.
When authentication is successful, Authentication Service activates the session by calling the appropriate methods in the Session Service.
Authentication Service stores information such as Login time, Authentication Scheme, and Authentication Level in the session data structure.
Once the session is activated, Session Service changes the state of the session token to valid.
The Distributed Authentication User Interface replies to the protected resource with an SSOToken in a set-cookie header.
The browser makes a request to the originally requested resource protected by an Agent.
This time, the request includes the valid session data structure and session token that were created during the authentication process. The next part of the user session is Session Validation.