Before you begin
Java 2 Platform, Enterprise Edition (J2EE) Connector authentication
data entries are used by resource adapters and Java DataBase Connectivity
(JDBC) data sources. A J2EE Connector authentication data entry contains authentication
data, which includes the following information:
- Alias
- An identifier that identifies the authentication data entry. When configuring
resource adapters or data sources, the administrator can specify which authentication
data to choose using 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.
This task creates and deletes Java 2 Connector (J2C) authentication
data entries.
Steps for this task
- Delete a J2C authentication data entry.
- Click Security > Global security.
- Under Authentication, click JAAS configuration > J2C authentication
data. The J2C Authentication Data Entries panel is displayed.
- 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 data source.
If the deleted authentication data entry is used or referenced by a resource,
the application that uses the resource adapter or the data source fails to
connect to the resources.
- Create a new J2C authentication data entry.
- Click Security > Global security.
The J2C Authentication Data Entries panel is displayed.
- Under Authentication, click JAAS configuration > J2C authentication
data. The J2C Authentication Data Entries panel is displayed.
- Click New.
- Enter a unique alias, a valid user ID, a valid password, and
a short description (optional).
- Click OK or Apply. No validation for
the user ID and password is required.
- Click Save. For a Network Deployment installation,
make sure that a file synchronized operation is performed to propagate the
changes to other nodes.
Result
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 to 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 application server when starting an application and is
shared among applications in the same application server.
If you create
or update a data source that points to a newly created J2C authentication
data alias, the test connection fails to connect until you restart the deployment
manager. After 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.
What to do next
This step defines authentication data that you can share among resource
adapters and data sources. Use the authentication data entry that is defined
in the resource adapters or the data sources.