Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Enabling Authentication and Authorization for the EAI JMS Transport >

Configuring Credentials in JNDI

JNDI credentials are specified in the jndi.properties file by setting java.naming.security.principal to the username and java.naming.security.credentials to the password. For more details, refer to the JNDI specification. The construction of the naming context automatically reads the credentials from the jndi.properties file and uses those credentials to connect to a JNDI server if authentication is required to perform JNDI lookup.

For security reasons, Siebel CRM requires that the value of java.naming.security.credentials (representing the JNDI password) in the jndi.properties file be encrypted. The JNDIEncryptionCheck parameter in the JMSSubsys named subsystem is set to TRUE by default to enforce the encryption requirement. In this case, Siebel CRM decrypts the encrypted value of java.naming.security.credentials.

NOTE:  JNDIEncryptionCheck is TRUE in all newly created named subsystems based on JMSSubsys. For any older subsystems in which JNDIEncryptionCheck is not set to TRUE, the java.naming.security.credentials value in the jndi.properties file is not treated as an encrypted value.

Customers encrypt the value of java.naming.security.credentials in the jndi.properties file by using the following encryption utilities:

• EncryptJndi.sh, found in the <SIEBEL_ROOT>/ses/siebsrvr/bin folder on UNIX
• EncryptJndi.bat, found in the <SIEBEL_ROOT>\ses\siebsrvr\bin folder on Windows