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.
- Configure a user registry.
- Configure WebSEAL
- Configure SSO
- Propagate security attributes.
- Configure the authentication cache.
What to do next
After completing the configuring the authentication process, authorize access to resources.
Subtopics
- Characters that are valid for user IDs and passwords
- Select an authentication mechanism
- Single sign-on for authentication
- Configure an OpenID Connect Relying Party
- OpenID Connect overview
- Configure an OpenID Relying Party
- OpenID authentication overview
- Configure administrative authentication
- Job manager security
- JAAS
- Use the JAAS programming model for web authentication
- Performing identity mapping for authorization across servers in different realms
- Security attribute propagation
- Configure CSIv2 inbound and outbound communication settings
- Authentication protocol for EJB security
- Use Microsoft Active Directory for authentication
- SAML web single sign-on
Related:
Trust associations