Select a J2C authentication alias
Select a Java 2 Connector (J2C) authentication alias for the resource that we are configuring
This page is available only when at least one security domain is defined and assigned a scope that is applicable to the resource being used edited. Additionally, that security domain must contain at least one JAAS J2C Authentication alias. Security domains isolate J2C authentication aliases between servers.
The tree view is useful in determining the security domain to which an alias belongs, and the tree view can help you determine the servers that are able to access each authentication alias. The tree view is tailored for each resource, so domains and aliases are hidden when we cannot use them. For example, a cell-scoped security domain is hidden from the tree if all servers and clusters in the tree have defined their own security domain. If we are looking for an alias that is not visible in the tree, it is because the alias cannot be used by any servers that have visibility to this resource. In this case, define the alias at the global scope or in a different security domain that is visible to this resource.
To view this administrative console page:
- Read the preceding introduction for conditions under which this page is accessible.
- Click one of the following paths in the administrative console:
- Resources > JDBC > Data sources > data_source. Click Browse... in the security settings section for the applicable authentication classes.
- Resources > JDBC > JDBC providers > jdbc_provider > Data sources > data_source. Click Browse... in the security settings section for the applicable authentication classes.
- Resources > Resource Adapters > J2C connection factories > j2c_connection_factory. Click Browse... in the security settings section for the applicable authentication classes.
- Resources > Resource Adapters > J2C activation specifications > j2c_activation_specification. Click Browse... in the security settings section for the applicable authentication classes.
- Resources > JMS > Connection factories > connection_factory. Click Browse... in the security settings section for the applicable authentication classes.
- Resources > JMS > JMS providers > jms_provider > [Additional properties] Queue connection factories > connection_factory. Click Browse... in the security settings section for the applicable authentication classes.
- Applications > Application Types > WebSphere enterprise applications > application > [Modules] Manage Modules > module > [Additional Properties] Resource Adapter > [Additional Properties] J2C connection factories > connection_factory. Click Browse... in the security settings section for the applicable authentication classes.
- Applications > Application Types > WebSphere enterprise applications > application > [Modules] Manage Modules > module > [Additional Properties] Resource Adapter > [Additional Properties] J2C activation specifications > activation_spec. Click Browse... in the security settings section for the applicable authentication classes.
Be careful when selecting an alias, because it is possible to select an alias that is only accessible by a subset of the servers that use the resource. If we select a global alias, we are guaranteed an alias by that name is accessible to all users of the resource. If the alias has been overridden in a security domain, however, that alias is used instead of the global one. The tree view includes icons to help we select the proper alias:
The alias is accessible by all servers that can access this resource.
There is at least one server that cannot access the alias.
Check the tree view to see if this is OK for the application that will be using this resource.
The alias is defined in multiple places.