Configuring authentication aliases for Liberty

You can configure an authentication data alias to use with a resource reference for authentication in Liberty.

About this task

To avoid having to code user IDs and passwords for data sources in your applications, you can configure the application server to use authentication data to provide the user IDs and passwords. For resources that use container authentication, you can configure authentication data and aliases in several ways, some of which include:

  • Create a unique authentication data element (authData) with the proper credentials and refer to it in your application bindings file.
  • Create a unique authentication data element (authData) with the proper credentials and make it the default container authentication for a data source by referring to it with containerAuthDataRef on the dataSource element.
  • Create a container default authentication element (containerAuthData) with the necessary credentials. You don't need to refer to the alias or the name of the authData element in your application bindings file.

Creating an authData element enables each resource reference to a data source to use different authentication credentials. The containerAuthData element establishes default credentials for container authentication in the absence of an authentication alias in the bindings for a resource reference.

Note: Unlike WebSphere® Application Server traditional, Liberty has no authentication alias principal mapping module support.

Procedure


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Saturday, 3 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twlp_sec_jca
File name: twlp_sec_jca.html