Implementation Guide › Configuration Considerations › Authentication and a Centralized Login Server › Centralize Login Pages

Centralize Login Pages

Application login requirements can range from basic user name/password authentication to forms–based authentication to digital certificates. If possible, we recommend:

• Managing all login pages from a central login server to avoid duplication on every web application.
• Managing all other system–wide resources, such as password services pages, error pages, and terms and conditions pages from a central server.

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

Managing login pages centrally is the process of identifying applications that share the same login requirements. Consider the following when configuring authentication:

• Try to avoid creating separate login pages for each application. As SiteMinder adoption increases, managing a login page for every application may not be sustainable.
• Identify applications that share the same authentication requirements. If possible, use a single login page as an entry point into these applications.

Use a table similar to the following to group applications by authentication requirements:

Example: Grouping applications by authentication requirements

A SiteMinder environment protects ten applications:

• Five of the applications require forms-based authentication.
• Three of the applications require Windows-based authentication.
• Two of the applications require basic user name/password authentication.

  By identifying applications that share the same authentication requirements, three login pages replace the need for eight, as detailed by the following table: