Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Application Server Configuration Notes | WebSphere Server | Security | JNDI Authentication
 
JNDI Authentication
JNDI provides the following security-related properties that, if provided by the client, are passed into the WebSphere naming service implementation:
*java.naming.security.protocol
*java.naming.security.authentication
*java.naming.security.principal
*java.naming.security.credentials
Though we have performed no testing in this area, it appears that WebSphere does not recognize these four properties. Instead, it uses the property settings in its sas.client.props file. This file defines IBM-specific properties that appear to mirror the functionality of the java.naming.security.* properties. The file contains embedded comments for each property.
*To ensure Adapter for Enterprise Javabeans uses the sas.client.props file for JNDI-specific credentials
1. Copy the sas.client.props to the Integration Server disk. Ensure that the target location is available to Integration Server's JVM.
This file is located on the WebSphere installation disk in the WAS-Install-Root-Dir\properties directory.
2. An Adapter for Enterprise Javabeans connection is then configured to use this file by setting the following property in the connection properties file:
com.ibm.CORBA.ConfigURL = file:path-to-sas.client.props
where path-to-sas.client.props is the full path to the sas.client.props file on the Integration Server disk.