Is it possible to use an encrypted password in a jndi.properties when integrating Siebel with TIBCO EMS?

Is it possible to use an encrypted password in a jndi.properties when integrating Siebel with TIBCO EMS?

book

Article ID: KB0089502

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
The jndi.properties file is used for client a configuration to make JNDI connection to the JNDI server. However, EMS does not manage this file.

The two parameters: java.naming.security.principal and java.naming.security.credentials defined in jndi.properties are used by
the standard javax.naming.InitialContex class provided by the JDK. It is outside of the EMS API. 

We do not read the properties file directly. Whatever code is doing the reading of the properties file is the point at which a mangled password could be de-mangled (encrypted or de-encrypted) before putting it into the environment where we can use it.

The Oracle Siebel application should be able to do something for this.  Ask the customer to confirm with Oracle which component is reading the properties file and transferring the information into the environment where the EMS jar file gets the information from.

Issue/Introduction

Is it possible to use an encrypted password in a jndi.properties when integrating Siebel with TIBCO EMS?