OID API+ User details access

Question

Hi,
We are using below API to get the user details defined in OID,
public static javax.naming.ldap.InitialLdapContext getDefaultDirCtx(java.lang.String host,
java.lang.String port,
java.lang.String bindDN,
java.lang.String bindPwd)
then create user object based on ldap context.Currently we read the bindDN and bindPwd from properties file. What is the best way to keep the bindPwd ? We dont want keep in properties file.

Answer 1

Enter the passphrase that controls access to the key on the command line when starting OC4J that portal runs on.OK. We used the ansatz from http://oracletechy.blogspot.com/2008_09_01_archive.html
Put a parameter in web.xml, say jndi-password:
<env-entry>
<description>Password for jndi</description>
<env-entry-name>jndi-password</env-entry-name>
<env-entry-value>thisisawrongpassword</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
Then read it in via
Context initial = new InitialContext();
Context environment = (Context)initial.lookup("java:comp/env");
st_jndi_password = (String)environment.lookup("jndi-password");
We use this for an hashtable
hashtable.put(Context.SECURITY_CREDENTIALS, st_jndi_password);
This is the input for an new
          InitialLdapContext(hashtable, null);
After the deployment the administrator must change the parameter jndi-password in the web.xml to the true OID passwort. But of course not by editing the file but using OC4J's OEM to change the environment variable.
But now we find the password in the file orion-web.xml which is not what we have intended....
Edited by: t142980 on Apr 7, 2009 8:59 AM