Implementation Guide › Configuration Considerations › Authentication and a Centralized Login Server › Login Page Use Cases › Stand–Alone Login Page

Stand–Alone Login Page

In this use case, SiteMinder directs users to a stand–alone login page when they request a protected resource. Specifically:

• A dynamic login page (login.asp) is deployed to the Web Agent host system.
• The dynamic login page is coded to:
  • Post to a login FCC file (login.fcc).
  • Display an error message when the SMTRYNO cookie is present in the web browser of the user.

    Note: For more information about the SMTRYNO cookie, see the Web Agent Configuration Guide.

• The login FCC file is configured with an @directive (@smretries) to redirect users to a failed authentication page (login.unauth) after two failed authentication attempts.

  Note: For more information about configuring an FCC file with @directives, see the Policy Server Configuration Guide.

• A SiteMinder administrator has configured a form–based authentication scheme named Auth1. The target of Auth1 is login.asp.

  Note: For more information about configuring authentication schemes, see the Policy Server Configuration Guide.

The following diagram illustrates the authentication process for this use case:

1. A user requests a protected resource.
2. The Web Agent contacts the Policy Server, which determines that the resource is protected.
3. The Web Agent redirects the user request to login.asp.
4. The user submits invalid credentials. The credentials are posted to the login.fcc file and processed by the FCC.
5. The FCC forwards the credentials to the Policy Server.
6. The Policy Server determines that the credentials are invalid and notifies the FCC.
7. The FCC inserts the SMTRYNO cookie into the web browser of the user and redirects the user to the login page.
8. The login page refreshes with an error message. The error message states that invalid credentials were supplied and to try again.
9. The user submits invalid credentials. The credentials are posted to the login.fcc file and processed by the FCC.
10. The FCC forwards the credentials to the Policy Server.
11. The Policy Sever determines that the credentials continue to be invalid and notifies the FCC.
12. The user has exceeded the maximum number of failed authentication attempts and is redirected to a page that displays a failed authentication message.