CSIv2 outbound authentication settings
Use this page to specify the features that a server supports when acting as a client to another downstream server.
To view this administrative console page, complete the following steps:
- Click Security > Global security.
- Under Authentication, click Authentication protocols > CSIv2 outbound authentication.
You also can view this administrative console page by completing the following steps:
- Click Servers > Application Servers > servername.
- Under Security, click Server security.
- Under Additional properties, click CSIv2 outbound authentication.
Authentication features include the following layers of authentication that use simultaneously:
- Transport layer
- The transport layer, the lowest layer, might contain a Secure Sockets Layer (SSL) client certificate as the identity.
- Message layer
- The message layer might contain a user ID and password or authenticated token.
- Attribute layer
- The attribute layer might contain an identity token, which is an identity from an upstream server that is already authenticated. The attribute layer has the highest priority, followed by the message layer and then the transport layer. If this server sends all three, only the attribute layer is used by the downstream server. The only way to use the SSL client certificate as the identity is if it is the only information presented during the outbound request.
- Client certificate authentication
Specifies whether a client certificate from the configured keystore is used to authenticate to the server when the SSL connection is made between this server and a downstream server (provided that the downstream server supports client certificate authentication).
Typically, client certificate authentication has a higher performance than message layer authentication, but requires some additional setup. These additional steps include verifying that this server has a personal certificate and that the downstream server has the signer certificate of this server.
If you select client certificate authentication, the following options are available:
- This option indicates that this server does not attempt Secure Sockets Layer (SSL) client certificate authentication with downstream servers.
- This option indicates that this server can use SSL client certificates to authenticate to downstream servers. However, a method can be invoked without this type of authentication. For example, the server can use anonymous or basic authentication instead.
- This option indicates that this server must use SSL client certificates to authenticate to downstream servers.
- Identity assertion
Specifies whether to assert identities from one server to another during a downstream enterprise bean invocation.
The identity asserted is the invocation credential that is determined by the RunAs mode for the enterprise bean. If the RunAs mode is Client, the identity is the client identity. If the RunAs mode is System, the identity is the server identity. If the RunAs mode is Specified, the identity is the identity specified. The receiving server receives the identity in an identity token and also receives the sending server identity in a client authentication token. The receiving server validates the identity of the sending server to ensure a trusted identity.
When specifying identity assertion on the CSIv2 Authentication Outbound panel, also select basic authentication as supported or required on the CSIv2 Authentication Outbound panel. The server identity can then be submitted with the identity token, so that the receiving server can trust the sending server. Without specifying basic authentication as supported or required, trust is not established and the identity assertion fails.
- Stateful sessions
Specifies whether to reuse security information during authentication. This option is usually used to increase performance.
The first contact between a client and server must fully authenticate. However, all subsequent contacts with valid sessions reuse the security information. The client passes a context ID to the server, and that ID is used to look up the session. The context ID is scoped to the connection, which guarantees uniqueness. When the security session is not valid and if authentication retry is enabled, which is the default, the client-side security interceptor invalidates the client-side session and resubmits the request transparently. For example, if the session does not exist on the server; the server fails and resumes operation.
When this value is disabled, every method invocation must authenticate again.
- Login configuration
Specifies the type of system login configuration that is used for outbound authentication.
You can add custom login modules before or after this login module by clicking Security > Global security. Under Authentication, click JAAS configuration > System login.
- Custom outbound mapping
Enables the use of custom RMI outbound login modules.
The custom login module maps or performs other functions before the predefined RMI outbound call. To declare a custom outbound mapping, click Security > Global security. Under Authentication, click JAAS configuration > System logins > New.
- Security attribute propagation
Enables WAS to propagate the Subject and the security content token to other application servers using the Remote Method Invocation (RMI) protocol.
Verify that you are using LTPA as your authentication mechanism. LTPA is the only authentication mechanism that is supported when you enable the security attribute propagation feature. To configure LTPA, click Security > Global security. Under Authentication, click Authentication mechanisms > LTPA.
By default, the Security attribute propagation option is enabled and outbound login configuration is invoked. If you clear this option, WebSphere Application Server does not propagate any additional login information to downstream servers.
- Trusted target realms
Specifies a list of trusted target realms, separated by a pipe character (|), that differ from the current realm.
Prior to WebSphere Application Server, V5.1.1, if the current realm does not match the target realm, the authentication request is not sent outbound to other application servers.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.