SAS and CSIv2 common settings for a client configuration
Overview
Edit the following settings in...
$WAS_HOME/properties/sas.client.props...to configure SAS and CSIv2 clients.
com.ibm.CORBA.securityEnabled
Enable/disable security for the client process.
Data type... Boolean Default... True Valid values... True or False
com.ibm.CSI.protocol
Set active authentication protocols.
The client can configure protocols of ibm, csiv2 or both as active. The only possible values for an authentication protocol are ibm, csiv2 and both. Do not use sas for the value of an authentication protocol. This restriction applies to both client and server configurations. The following list provides information about using each of these protocol options...
ibm Use if communicating with WAS version 4.x or previous version servers.
csiv2 Use if communicating with WAS v5 or later servers because the SAS interceptors are not loaded and running for each method request.
both Use for interoperability between WAS v4.x or previous and WAS v5 or later servers. Typically, specifying both provides greater interoperability with other servers.
Data type... String Default... Both Valid values... ibm, csiv2, both
com.ibm.CORBA.authenticationTarget
Set authentication mechanism for sending security information from the client to the server.
If basic authentication is specified, the user ID and password are sent to the server. Using the SSL transport with this type of authentication is recommended because otherwise the password is not encrypted. The target server must support the specified authenticationTarget.
If you specify LTPA, then LTPA must be the mechanism configured at the server for a method request to proceed securely.
Data type... String Default... BasicAuth Valid values... BasicAuth, LTPA
com.ibm.CORBA.validateBasicAuth
Determine if the user ID and password get validated immediately after the login data is entered when the authenticationTarget property is set to BasicAuth.
In past releases, BasicAuth logins only validated with the initial method request. During the first request, the user ID and password is sent to the server. This is the first time that the client can notice an error, if the user ID or password is incorrect. The validateBasicAuth method is specified and the validation of the user ID and password occurs immediately to the security server.
For performance reasons, you might want to disable this property if it is not desirable to verify the user ID and password immediately. If the client program can wait, it is better to have the initial method request flow to the user ID and password. However, program logic might not be as simple because of error handling considerations.
Data type... Boolean Default... True Valid values... True or False
com.ibm.CORBA.authenticationRetryEnabled
Use to specify that a failed login attempt is retried. This property determines if a retry occurs for other errors, such as stateful sessions that are not found on a server or validation failures at the server because of an expiring credential.
The minor code in the exception that is returned to a client determines which errors are retried. The number of retry attempts is dependent upon the property com.ibm.CORBA.authenticationRetryCount.
Data type... Boolean Default... True Valid values... True or False
com.ibm.CORBA.authenticationRetryCount
Use to specify the number of retries that occur until either a successful authentication occurs or the maximum retry value is reached.
When the maximum retry value is reached, the authentication exception is returned to the client.
Data type... Integer Default... 3 Range... 1-10
com.ibm.CORBA.loginSource
Use to specify how the request interceptor attempts to log in if it does not find an invocation credential already set.
This property is only valid if message layer authentication occurs. If only transport layer authentication occurs, this property is ignored. When specifying properties, the following two additional properties need to be defined:
When performing a programmatic login, it is not necessary to specify none as the login source. Unless you want the request to fail, do not set a credential as the invocation credential during a method request.
Data type... String Default... Prompt Valid values... prompt, key file, stdin, none, properties
com.ibm.CORBA.loginUserid
Use to specify the user ID when a properties login is configured and message layer authentication occurs.
This property is only valid when com.ibm.CORBA.loginSource=properties. Also, set the com.ibm.CORBA.loginPassword property.
Data type... String Range... Any string appropriate for a user ID in the configured user registry of the server.
com.ibm.CORBA.loginPassword
Use to specify the password when a properties login is configured and message layer authentication occurs.
This property is only valid when com.ibm.CORBA.loginSource=properties. Also, set the com.ibm.CORBA.loginUserid property.
Data type... String Range... Any string appropriate for a password in the configured user registry of the server
com.ibm.CORBA.keyFileName
Use to specify the key file that is used to log in.
A key file is a file that contains a list of realm, user ID, and password combinations that a client uses to log into multiple realms. The realm used is the one found in the Interoperable Object Reference (IOR) for the current method request. The value of this property is used when com.ibm.CORBA.loginSource=key file is used.
Data type... String Default... C:/WebSphere/AppServer/properties/wsserver.keyC:/WebSphere Range... Any fully qualified path and file name of a WebSphere Application Server key file
com.ibm.CORBA.loginTimeout
Use to specify the length in time that the login prompt stays available before it is considered a failed login.
Data type... Integer Units... Seconds Default... 300 (5 minute intervals) Range... 0 - 600 (10 minute intervals)
com.ibm.CORBA.securityEnabled
Determine if security is enabled for the client process.
Data type... Boolean Default... True Range... True or False