Common Secure Interoperability inbound authentication settings
Use this page to specify the features that a server supports for a client accessing its resources.
To view this administrative console page, click Security > Global security. Under Authentication, click Authentication protocols > CSIv2 inbound authentication.
You can also view this administrative console page, by clicking Servers > Application servers > servername. Under Security, click Server security. Under Additional properties, click CSIv2 inbound authentication.
Use common secure interoperability (CSI) inbound authentication settings for configuring the type of authentication information that is contained in an incoming request or transport.
Authentication features include three layers of authentication that use simultaneously:
- Transport layer. The transport layer, which is the lowest layer, might contain a SSL client certificate as the identity.
- Message layer. The message layer might contain a user ID and password or an authenticated token with an expiration.
- Attribute layer. The attribute layer might contain an identity token, which is an identity from an upstream server that already is authenticated. The identity layer has the highest priority, followed by the message layer, and then the transport layer. If a client sends all three, only the identity layer is used. The only way to use the SSL client certificate as the identity is if it is the only information that is presented during the request. The client picks up the interoperable object reference (IOR) from the namespace and reads the values from the tagged component to determine what the server needs for security.
- Basic authentication
Specifies that basic authentication occurs over the message layer.
In the message layer, basic authentication (user ID and password) takes place. This type of authentication typically involves sending a user ID and a password from the client to the server for authentication.
This authentication also involves delegating a credential token from an already authenticated credential, provided the credential type is forwardable (for example, LTPA).
If you select Basic Authentication and LTPA is the configured authentication protocol, user name, password, and LTPA tokens are accepted.
The following options are available for Basic Authentication:
- This option indicates that this server cannot accept user ID and password authentication.
- This option indicates that a client communicating with this server can specify a user ID and password. However, a method might be invoked without this type of authentication. For example, an anonymous or client certificate might be used instead.
- This option indicates that clients communicating with this server must specify a user ID and password for any method request.
Basic authentication takes precedence over client certificate authentication, if both are performed.
- Client certificate authentication
Specifies that authentication occurs when the initial connection is made between the client and the server during a method request.
In the transport layer, SSL client certificate authentication occurs. In the message layer, basic authentication (user ID and password) is performed. Client certificate authentication typically performs better than message layer authentication, but requires some additional setup. These additional steps involve verifying that the server trusts the signer certificate of each client to which it is connected. If the client uses a certificate authority (CA) to create its personal certificate, you only need the CA root certificate in the server signer section of the SSL trust file.
When the certificate is authenticated to a Lightweight Directory Access Protocol (LDAP) user registry, the distinguished name (DN) is mapped based on the filter that is specified when configuring LDAP. When the certificate is authenticated to a LocalOS user registry, the first attribute of the distinguished name (DN) in the certificate, which is typically the common name, is mapped to the user ID in the registry.
The identity from client certificates is used only if no other layer of authentication is presented to the server.
The following options are available for Client certificate authentication:
- This option indicates that clients cannot attempt Secure Sockets Layer (SSL) client certificate authentication with this server.
- This option indicates that clients connecting to this server can authenticate using SSL client certificates. However, the server can invoke a method without this type of authentication. For example, anonymous or basic authentication can be used instead.
- This option indicates that clients connecting to this server must authenticate using SSL client certificates before invoking the method.
- Identity assertion
Specifies that identity assertion is a way to assert identities from one server to another during a downstream EJB invocation.
This server does not authenticate the asserted identity again because it trusts the upstream server. Identity assertion takes precedence over all other types of authentication.
Identity assertion is performed in the attribute layer and is only applicable on servers. The principal determined at the server is based on precedence rules. If identity assertion is performed, the identity is always derived from the attribute layer. If basic authentication is performed without identity assertion, the identity is always derived from the message layer. Finally, if SSL client certificate authentication is performed without either basic authentication, or identity assertion, then the identity is derived from the transport layer.
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 one 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 sending server identity as a trusted identity through the Trusted Server IDs entry box. Enter a list of pipe-separated (|) principal names, for example, serverid1|serverid2|serverid3.
All identity token types map to the user ID field of the active user registry. For an ITTPrincipal identity token, this token maps one-to-one with the user ID fields. For an ITTDistinguishedName identity token, the value from the first equal sign is mapped to the user ID field. For an ITTCertChain identity token, the value from the first equal sign of the distinguished name is mapped to the user ID field.
When authenticating to an LDAP user registry, the LDAP filters determine how an identity of type ITTCertChain and ITTDistinguishedName get mapped to the registry. If the token type is ITTPrincipal, then the principal gets mapped to the UID field in the LDAP registry.
Data type: String
- Trusted servers
Use this list to decide whether a server is trusted. Even if the server is on the list, the sending server must still authenticate with the receiving server to accept the identity token of the sending server.
Data type String
- Stateful sessions
Specifies stateful sessions that are used mostly for performance improvements.
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 the ID is used to look up the session. The context ID is scoped to the connection, which guarantees uniqueness. Whenever the security session is not valid and the authentication retry is enabled, which is the default, the client-side security interceptor invalidates the client-side session and submits the request again without user awareness. This situation might occur if the session does not exist on the server (the server failed and resumed operation). When this value is disabled, every method invocation must authenticate again.
Data type String
- Login configuration
Specifies the type of system login configuration to use for inbound authentication.
You can add custom login modules by clicking Security > Global security. Under Authentication, click JAAS configuration > System logins.
- Security attribute propagation
Specifies whether to support security attribute propagation during login requests. When you select this option, WebSphere Application Server retains additional information about the login request, such as the authentication strength used, and retains the identity and location of the request originator.
Verify that you are using LTPA as your authentication mechanism. LTPA is the only authentication mechanism supported when you enable the security attribute propagation feature. To configure LTPA, click Security > Global security. Under Authentication, click Authentication mechanisms > LTPA.
If you do not select this option, WAS does not accept any additional login information to propagate to downstream servers.
System login configuration entry settings for Java Authentication and
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.