Manage J2EE Connector Architecture authentication data entries

 

This task creates and deletes Java 2 Connector (J2C) authentication data entries. Java 2 Connector authentication data entries are used by resource adapters and JDBC data sources. A Java 2 Connector authentication data entry contains authentication data, which contains the following information:

 

Alias

An identifier used to identify the authenticated data entry. When configuring resource adapters or Java database connectivity (JDBC) data sources, the administrator can specify which authentication data to choose for the corresponding alias.

 

User ID

A user identity of the intended security domain. For example, if a particular authentication data entry is used to open a new connection to DB2, this entry contains a DB2 user identity.

 

Password

The password of the user identity is encoded in the configuration respository.

 

Description

A short text description.

 

  1. Delete a J2C authentication data entry.

    1. Click Security in the navigation tree, then click JAAS Configuration > J2C Authentication Data. This navigates to the J2C Authentication Data Entries panel.

    2. Select the check boxes for the entries to delete and click Delete. Before deleting or removing an authentication data entry, make sure that it is not used or referenced by any resource adapter or JDBC data source. If the deleted authentication data entry is used or referenced by a resource, the application that uses the resource adapter or JDBC data source fails to connect to the resources.

  2. Create a new J2C authentication data entry.

    1. Click Security in the navigation tree, then click JAAS Configuration > J2C Authentication Data. This will navigate to the J2C Authentication Data Entries panel.

    2. Click New.

    3. Enter a unique alias, a value user ID, a valid password, and a short description (optional).

    4. Click OK or Apply. There is no validation for the user ID and password.

    5. Click Save. For a Network Deployment installation, make sure a file synchronized operation is performed to propagate the changes to other nodes.

 

Results

A new J2C authentication data entry is created or an old entry is removed. The newly created entry is visible without restarting the application server process for use in the data source definition. But the entry is only in effect after the server is restarted. Specifically, the authentication data is loaded by an appserver when starting an application and is shared among applications in the same appserver.

If you create or update a data source that points to a newly created J2C authentication data alias, Test Connection fails to connect until you have restarted the deployment manager. Once you restart the deployment manager, the J2C authentication data is reflected in the run-time configuration. Any changes to the J2C authentication data fields require a deployment manager restart for the changes to take effect.

 

Usage scenario

This step defines authentication data that you can share among resource adapters and JDBC data sources.

 

What to do next

Use the authentication data entry defined in the resource adapters or JDBC data sources.

Programmatic login
Java 2 Connector authentication data entry settings

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.