J2CA0130I: Data Source <datasource> has component-managed Authentication Alias <authentication alias> but no corresponding J2C Authentication Data Entry is defined in security.xml
 Technote (troubleshooting)
 
Problem(Abstract)
J2CA0130I: Data Source <CorporateDB> has Component-managed Authentication Alias <esb-ws-deployManager/EmigrantApp> but no corresponding J2C Authentication Data Entry is defined in security.xml. This can have undesirable effects.

WSVR0049I: Binding CorporateDB as jdbc/Corporate

DSRA8040I: Failed to connect to the DataSource. Encountered : java.lang.Exception: java.sql.SQLException: [IBM][SQLServer JDBC Driver]Could not establish a connection using integrated security: No LoginModules configured for JDBC_DRIVER_01
 
Cause
The Data Source, CorporateDB, has a Component-managed Authentication Alias
<esb-ws-deployManager/EmigrantApp> mapped as shown below but it has no corresponding J2C Authentication Data Entry defined in the security.xml

Datasource Factory Definition from the resources.xml file:

<factories xmi:type="resources.jdbc:DataSource" xmi:id="DataSource_1082731835905" name="CorporateDB" jndiName="jdbc/Corporate" description="New JDBC Datasource" authMechanismPreference="BASIC_PASSWORD" authDataAlias="esb-ws-deployManager/EmigrantApp" statementCacheSize="10" datasourceHelperClassname="com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper" relationalResourceAdapter="builtin_rra">

Possible causes:
  1. The datasource definition was copied from one system to another manually without copying the corresponding J2C Authentication alias from the security.xml.
  2. The security.xml and resources.xml files were edited manually and introduced a mismatch in the alias names.
  3. Some error prevented the authentication aliases from being read from the security.xml file. For example:

[8/11/08 8:42:27:309 EDT] 0000000a ContainerImpl E WSVR0501E: Error
creating component com.ibm.ws.security.core.SecurityComponentImpl
java.lang.NoClassDefFoundError: com/ibm/crypto/fips/provider/IBMJCEFIPS
at
com.ibm.ws.security.core.distSecurityComponentImpl.getSSLConfigPropertie
s(distSecurityComponentImpl.java:947)
at
com.ibm.ws.security.core.distSecurityComponentImpl.initializeDefaultSSLS
ettings(distSecurityComponentImpl.java:899)
 
Resolving the problem
Use the IBM® WebSphere® Application Server Administrative Console to create the J2C Authentication Data Entry EmigrantApp, then restart the Server.
Configuring J2C authentication data Entry
  1. Select Administrative Console > Select Security > JAAS Configuration > J2C Authentication Data.

  2. Click New, then specify the following information to create the authentication data.
The name of the security information entry (in this case, EmigrantApp)

User ID
The user ID for this alias

Password
The password for this alias

Description
An optional (but recommended) description of the alias

After creating the J2C authentication data Entry, update the security.xml with the following entry:

<authDataEntries xmi:id="JAASAuthData_1062972259062" alias=""esb-ws-deployManager/EmigrantApp" userId="user" password="{xor}PT4zPm4v" description="some thing meaningful to this context"/>

esb-ws-deployManager is the Node name, which is appended automatically.

3. If the authentication data is in the security.xml file, then check the SystemOut.log and SystemErr.log to see if there are any errors that might have caused the processing of the security configuration to fail to complete. Address the error that prevented the security configuration from being processed.
 
The attached stack.txt file has the detailed stack trace from the SystemOut

stack.txt
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): i5/OS
Software version: 7.0
Software edition:
Reference #: 1168908
IBM Group: Software Group
Modified date: Oct 30, 2008