EncryptJNDI failing with error connecting to server manager and not encrypting jndi.properties. (Doc ID 1937032.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version [IP2013] and later
Information in this document applies to any platform.


Product Type: Siebel CRM
Version: [IP2013]
OS platform: Linux x86-64
DB: Oracle Database - Enterprise Edition
Env type: Test

Statement of Issue:
The requirement is to start a JMS Receiver task to pick-up and process messages from a JMS queue. The following information is included in 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 will automatically read the credentials from the jndi.properties file and use those credentials to connect to a JNDI server if authentication is required to perform JNDI lookup.

In Siebel CRM version and later, and version and later, for security reasons Siebel CRM enforces that the jndi.properties file must be encrypted using the scripts provided with the installation. The JNDIEncryptionCheck parameter in the JMSSubsys named subsystem is set to TRUE by default, so Siebel CRM requires that jndi.properties be encrypted. All newly created named subsystems based on JMSSubsys will have this security enforced, whereas older ones will continue to work with nonencrypted jndi.properties files.

In Siebel CRM version and later, and version 8.2, the following encryption utilities are available:

EncryptJndi.sh, found in the /ses/siebsrvr/bin folder on UNIX
EncryptJndi.bat, found in the \ses\siebsrvr\bin folder on Windows”

1) When EncryptJndi.sh was executed, it failed with an error trying to connect to server manager to set JNDIEncryptionSeed for the JMS Subsys.

2) Also, jndi.properties was not encrypted .




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms