CSIv2 inbound communications settings

Network Deployment (Distributed operating systems), v8.0 > Reference > Sets

CSIv2 inbound communications settings

Configure to accomodate authentication information contained within incoming requests and transports...

Security | Global security | Authentication | RMI/IIOP security | CSIv2 inbound communications

Layers of authentication...

CSIv2 attribute layer Can contain an identity token from an authenticated upstream server. 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. To use SSL client certificates as the identity have it be the only information 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.
CSIv2 transport layer Lowest layer. Might contain an SSL client certificate as the identity.
CSIv2 message layer Might contain a user ID and password or an authenticated token with an expiration.

Settings

Propagate security attributes

Default: Enabled
Supports security attribute propagation during login requests. The appserver retains...

Additional information about the login request, such as the authentication strength,
The identity and location of the request originator

If not selected, the appserver does not accept any additional login information to propagate to downstream servers.
If you use the replication services, ensure it is enabled.

Use identity assertion

Default: Disabled
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 appservers. The principal determined at the server is based on precedence rules.

If identity assertion is used, the identity is always derived from the attribute layer.

If basic authentication is used without identity assertion, the identity is always derived from the message layer.

If SSL client certificate authentication is performed without either basic authentication, or identity assertion, 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.

Trusted identities

Trusted identity that is sent from the sending server to the receiving server.
Specifies a pipe-separated (|) list of trusted server administrator user IDs, which are trusted to perform identity assertion to this server. For example...

serverid1|serverid2|serverid3

WAS v8 supports the comma (,) character as the list delimiter for backwards compatibility. The application server checks the comma character when the pipe character (|) fails to find a valid trusted server ID.
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.

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 used. 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 LDAP user registry, the distinguished name (DN) is mapped based on the filter specified when configuring LDAP. When the certificate is authenticated to a local OS 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.

Never Clients cannot attempt SSL client certificate authentication with this server.
Supported 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.
Required Clients connecting to this server must authenticate using SSL client certificates before invoking the method.

Transport

Default: SSL-required
Whether client processes connect to the server using one of its connected transports.
We can choose either SSL, TCP/IP or both as the inbound transport that a server supports. If you specify TCP/IP, the server only supports TCP/IP and cannot accept SSL connections. If you specify SSL-supported, this server can support either TCP/IP or SSL connections. If you specify SSL-required, then any server communicating with this one must use SSL.
This option is not available on the z/OS platform unless both v6.1 and earlier nodes exist in the cell.

TCP/IP The server opens a TCP/IP listener port only and all inbound requests do not have SSL protection.
SSL-required The server opens an SSL SSL listener port only and all inbound requests are received using SSL.
SSL-supported The server opens both a TCP/IP and an SSL listener port and most inbound requests are received using SSL.

Provide a fixed port number for the following ports. A zero port number indicates that a dynamic assignment is made at run time.

CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS

Range: TCP/IP, SSL Required, SSL-Supported

SSL settings

Specifies a list of predefined SSL settings to choose from for inbound connection.
Default: DefaultSSLSettings DefaultIIOPSSL
Range: SSL settings configured in the SSL Configuration Repertoire

Message layer authentication

The following options are available for message layer authentication:

Never Server cannot accept authentication using any of the mechanisms selected below.
Supported A client communicating with this server can authenticate using any of the mechanisms selected below. However, a method might be invoked without this type of authentication. For example, an anonymous or client certificate might be used instead.
Required Clients communicating with this server must specify authentication information using of the mechanisms selected below for any method request.

Allow client to server authentication with:

Specifies client-to-server authentication using Kerberos, LTPA or Basic authentication.
The following options are available for client to server authentication:

Kerberos (KRB5) Specify Kerberos as the authentication mechanism. We must first configure the Kerberos authentication mechanism. Read about Configure Kerberos as the authentication mechanism for more information.
LTPA LTPA token authentication
Basic authentication Generic Security Services Username Password (GSSUP). Typically involves sending a user ID and a password from the client to the server.

If you select Basic Authentication and LTPA, and the active authentication mechanism is LTPA, a user name, password, and LTPA tokens are accepted.
If you select Basic Authentication and KRB5 and the active authentication mechanism is KRB5, a user name, password, Kerberos token and LTPA tokens are accepted.
If you do not select Basic Authentication, a user name and password are not accepted by the server.

Login configuration

Type of system login configuration to use for inbound authentication.
We can add custom login modules by clicking Security > Global security. From Authentication, click JAAS > System logins.

Stateful sessions

Select this option to enable stateful sessions, which 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; for example, the server failed and resumed operation. When this value is disabled, each method invocation must authenticate again.
Default: Enabled

Trusted authentication realms - inbound

Select this link to establish inbound trust for realms. Inbound authentication realm settings are not specific to CSIv2; you can also configure which realms to grant inbound trust to for multiple security domains.
Inbound authentication refers to the configuration that determines the type of accepted authentication for inbound requests. This authentication is advertised in the IOR that the client retrieves from the name server.

Related
Configure CSIv2 inbound communications
System login configuration entry settings for JAAS
LTPA

+
Search Tips | Advanced Search

CSIv2 attribute layer	Can contain an identity token from an authenticated upstream server. 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. To use SSL client certificates as the identity have it be the only information 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.
CSIv2 transport layer	Lowest layer. Might contain an SSL client certificate as the identity.
CSIv2 message layer	Might contain a user ID and password or an authenticated token with an expiration.

Never	Clients cannot attempt SSL client certificate authentication with this server.
Supported	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.
Required	Clients connecting to this server must authenticate using SSL client certificates before invoking the method.

TCP/IP	The server opens a TCP/IP listener port only and all inbound requests do not have SSL protection.
SSL-required	The server opens an SSL SSL listener port only and all inbound requests are received using SSL.
SSL-supported	The server opens both a TCP/IP and an SSL listener port and most inbound requests are received using SSL.

Never	Server cannot accept authentication using any of the mechanisms selected below.
Supported	A client communicating with this server can authenticate using any of the mechanisms selected below. However, a method might be invoked without this type of authentication. For example, an anonymous or client certificate might be used instead.
Required	Clients communicating with this server must specify authentication information using of the mechanisms selected below for any method request.

Kerberos (KRB5)	Specify Kerberos as the authentication mechanism. We must first configure the Kerberos authentication mechanism. Read about Configure Kerberos as the authentication mechanism for more information.
LTPA	LTPA token authentication
Basic authentication	Generic Security Services Username Password (GSSUP). Typically involves sending a user ID and a password from the client to the server.