Authenticating users
The process of authenticating users involves a user registry and an authentication mechanism. Optionally, we can define trust between WebSphere Application Server and a proxy server, configure single sign-on capability, and specify how to propagate security attributes between application servers.
The following security topics are covered in this section:
The following information is covered in this section:
What to do next
After completing the configuring the authentication process, you must authorize access to resources. For more information, see Authorizing access to resources.
Subtopics
- Characters that are valid for user IDs and passwords
- Select a registry or repository
- Integrate third-party HTTP reverse proxy servers
- Implement single sign-on to minimize web user authentications
- (v8.5.5.3) Configure an OpenID Connect Relying Party
- (v8.5.5.3) OpenID Connect overview
- (v8.5.5.3) Configure an OpenID Relying Party
- (v8.5.5.3) OpenID authentication overview
- Configure administrative authentication
- Java Authentication and Authorization Service
- Use the JAAS programming model for web authentication
- Security attribute propagation
- Propagating security attributes among application servers
- Configure the authentication cache
- CSIV2 inbound and outbound communication settings
- Authentication protocol for EJB security
- Use Microsoft Active Directory for authentication
- SAML web single sign-on
Related concepts
Trust associationsAuthorizing access to resources