If you enable security for a WebSphere Application Server cell, supply authentication information to communicate with servers.
The nature of the properties file updates required for running in secure mode depend on whether you connect with a Remote Method Invocation (RMI) connector, or a Simple Object Access Protocol (SOAP) connector:
com.ibm.CORBA.loginUserid= com.ibm.CORBA.loginPassword=Also, set the following property:
com.ibm.SOAP.securityEnabled=true com.ibm.SOAP.loginUserid= com.ibm.SOAP.loginPassword=
Note: To use an RMI connector you must log in using a user ID that has a SAF keyring defined.
To specify the user and password information, choose one of the following methods:
wsadmin.sh -conntype RMI -port 2809 -user u1 -password secret1
If you specify user and password information on a command line in addition to specifying it in the sas.client.props file or the soap.client.props file, the command line information overrides the information in the props file.
The Remote Method Invocation (RMI) connector can be used securely without configuring Secure Sockets Layer (SSL) if you are using a user ID and password. If you want to configure SSL, use the Common Secure Interoperability Version 2 (CSIv2) properties and also set up a System Authorization Facility (SAF) keyring. The com.ibm.CORBA.loginUserid and com.ibm.CORBA.loginPassword properties are equivalent to the CSIv2 com.ibm.CSI.Rem.Userid and com.ibm.CSI.Rem.Password properties, respectively. Consequently, you do not need to configure both sets of properties. Simply add com.ibm.CSI.performSSL.Keyring=yourKeyring to the existing sas.client.props configuration and create the SAF keyring. Refer to Warning: no string named [tsec_sslconsideradmin] found. for additional information about creating keyrings, and refer to Warning: no string named [usec_csiv2init] found. for additional information about CSIv2 properties.