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

Authentication and a Centralized Login Server

A SiteMinder deployment typically includes applications for which different authentication (login) requirements exist. These requirements can result in numerous login pages that the individual application owners must manage. Managing these login pages locally can introduce inconsistencies, such as page design and the presentation of error messages, that can affect the overall authentication experience.

We recommend managing login pages centrally to help:

• Create consistency across your applications. If a single SiteMinder team owns all login pages, the team can implement them consistently and manage them easier.
• Minimize the number of login pages. Minimizing the number of entry points into applications creates the impression that users are logging into a centralized infrastructure, rather than individual applications.

Consider the following when configuring login pages:

• Identify applications that share the same authentication requirements and reuse the same login page.
• Use a centralized login server to host all login pages
• Configure login pages to inform users when:
  • They have failed to provide valid credentials.
  • Too many attempts have resulted in a failed authentication.