Common Secure Interoperability Version 2 and Security Authentication Service (SAS) client configuration

A secure Java™ client requires configuration properties to determine how to perform security with a server.

These configuration properties are typically put into a properties file somewhere on the client system and referenced by specifying the following system property on the command line of the Java client. For example, this property accepts any valid web address.

[AIX Solaris HP-UX Linux Windows][IBM i]

-Dcom.ibm.CORBA.ConfigURL=file:profile_root/properties/sas.client.props

[IBM i]When you use thin or thick clients, com.ibm.CORBA.ConfigURL is automatically set to the following file: 
profile_root/properties/sas.client.props

[AIX Solaris HP-UX Linux Windows][IBM i]When this file is processed by the Object Request Broker (ORB), security can be enabled between the Java client and the target server.

[AIX Solaris HP-UX Linux Windows][IBM i]If any syntax problems exist with the ConfigURL property and the sas.client.props file is not found, the Java client proceeds to connect insecurely. Errors display indicating the failure to read the ConfigURL property. Typically the problem is related to having two slashes after file, which is not valid.

[AIX Solaris HP-UX Linux Windows][IBM i]Use the following properties to configure the Secure Authentication Service (SAS) and CSIv2 authentication protocols:
Important: SAS is supported only between Version 6.0.x and previous version servers that have been federated in a Version 6.1 cell.