Password Indirection For ContextScanningResourceProvider (Doc ID 987857.1)

Last updated on NOVEMBER 05, 2016

In this Document
  Symptoms
  Cause
  Solution
  References


Symptoms

Currently the password property of com.evermind.server.deployment.ContextScanningResourceProvider, can only use a plain text password field for authentication with the backend, it is not possible to use password indirection. For example:

<resource-provider 
class="com.evermind.server.deployment.ContextScanningResourceProvider" 
name="TibcoJMSReference"> 
       <property 
           name="java.naming.factory.initial" 
           value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"> 
       </property> 
       <property 
           name="java.naming.provider.url" 
           value="tibjmsnaming://localhost:7222"> 
       </property> 
       <property 
           name="java.naming.security.principal" 
           value="shemp"> 
       </property> 
       <property 
           name="java.naming.security.credentials" 
           value="welcome1"> 
       </property> 
   </resource-provider> 

Basic security standards require all passwords to be never stored in plain text.

Password indirection allows the resource to look up the encrypted password that is needed for the authentication with the external resource via OC4J's standard password indirection functionality -- would therefore be easy to maintain and use. With this setup, no plain text password need to be used in configuration setup.

Cause

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