Common Secure Interoperability V2 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 console page, complete the following steps:
- Click Security > Secure administration, applications, and infrastructure.
- Under Authentication, click RMI/IIOP security > CSIv2 outbound authentication.
You also can view this console page by completing the following steps:
- Click Servers > Application Servers > server.
- Under Security, click Server security.
- Click CSIv2 outbound authentication.
Authentication features include the following layers of authentication used to 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 - the attribute layer, the message layer, and the transport layer - 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.
Configuration tab
- Client certificate authentication
Specify 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:
- Never
- This option indicates that this server does not attempt Secure Sockets Layer (SSL) client certificate authentication with downstream servers.
- Supported
- 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.
- Required
- This option indicates that this server must use SSL client certificates to authenticate to downstream servers.
- Identity assertion
Specify 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 inbound 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.
- Use server trusted identity
- Server identity that the appserver uses to establish trust with the target server. The server identity can be sent using one of the following methods:
- A server ID and password when the server password is specified in the registry configuration.
- A server ID in a LTPA token when the internal server ID is used.
For interoperability with appservers other than WebSphere Application Server, use one of the following methods:
- Configure the server ID and password in the registry.
- Select the Specify an alternative trusted identity option and specify the trusted identity and password so that an interoperable Generic Security Services Username Password (GSSUP) token is sent instead of an LTPA token.
- Specify an alternative trusted identity
Specify an alternative user as the trusted identity that is sent to the target servers instead of sending the server identity. This option is recommended for identity assertion. The identity is automatically trusted when it is sent within the same cell and does not need to be in the trusted identities list within the same cell. However, this identity must be in the registry of the target servers in an external cell and the user ID must be on the trusted identities list or the identity is rejected during trust evaluation.
- Trusted identity
- Timerusted identity that is sent from the sending server to the receiving server.
If you specify an identity in this field, it can be selected on the panel for your configured user account repository. If you do not specify an identity, a LTPA token is sent between the servers.
- Password
- Password that is associated with the trusted identity.
- Confirm password
- Confirms the password that is associated with the trusted identity.
- Stateful sessions
Specify 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
Timeype of system login configuration that is used for outbound authentication. You can add custom login modules before or after this login module by completing the following steps:
- Click Security > Secure administration, applications, and infrastructure.
- Under Authentication, click Java Authentication and Authorization Service > System logins > New.
- 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, complete the following steps:
- Click Security > Secure administration, applications, and infrastructure.
- Under Authentication, click Java Authentication and Authorization Service > System logins > New.
- Security attribute propagation
Enables the appserver to propagate the Subject and the security content token to other appservers 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 > Secure administration, applications, and infrastructure.
- Under Authentication, click Authentication mechanisms and expiration.
- Trusted target realms
Specify 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 appservers.
Related tasks
Configure Common Secure Interoperability V2 outbound authentication
Reference topic