WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Selecting an authentication mechanism

Why and when to perform this task

Information about users and groups reside in a user registry. In WebSphere Application Server, a user registry authenticates a user and retrieves information about users and groups to perform security-related functions, including authentication and authorization. Implementation is provided to support multiple operating system or operating environment-based user registries and most of the major Lightweight Directory Access Protocol (LDAP)-based user registries. You can use the custom LDAP feature to support any LDAP server by setting up the correct configuration (user and group filters). However, support is not extended to these custom LDAP servers because there are many possibilities that cannot be tested.

The next step in setting up security is to select an authentication mechanism. An authentication mechanism defines rules about security information. For example, the authentication mechanism determines whether a credential is forwardable to another Java process. The authentication mechanism defines the format of how security information is stored in both credentials and tokens. Authentication is the process of establishing whether a client is valid in a particular context. A client can be either an end user, a machine, or an application.

Although the Application Server provides several authentication mechanisms, only a single active authentication mechanism can be configured at one time. The active authentication mechanism is selected when configuring WebSphere Application Server global security. The following steps explain how to select the authentication mechanism that you want to use for your configuration.

Steps for this task

  1. Click Security > Global security.
  2. Under Authentication, expand Authentication mechanisms.
  3. Click the name of the authentication method that you want to use. Depending upon your product and platform, different authentication mechanism are available.

    To use Lightweight Third Party Authentication (LTPA) as your authentication mechanism, see Configuring the Lightweight Third Party Authentication mechanism.

What to do next

For more information on how to configure global security, see Enabling security for all application servers.



Sub-topics
Configuring the Lightweight Third Party Authentication mechanism

Related concepts
Authentication mechanisms
Lightweight Third Party Authentication
Trust associations
Single signon

Related tasks
Implementing single signon to minimize Web user authentications
Authenticating users

Related reference
Lightweight Third Party Authentication settings

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_authentication.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)