Brief Summary
The Domain Admin Console describes the usage of password aliases in lower case notation:
To get it working for JDBC Connection Pool passwords, the notation of the key must be upper case:
Expected Outcome
JDBC connection pool ping should succeed, if the password property uses a password alias as described in the Domain Admin Console.
Current Outcome
JDBC connection pool ping fails due to authentication error, if the descibed lower case notation ${alias=....} is used. Connection ping succeeds if upper case notation ${ALIAS=...} is used.
Reproducer
This can be reproduced by:
- defining a password alias for a database user password
- defining a JDBC connection pool (I tested it with PostgreSQL)
- ping the connection pool with plain text password to make sure connection is set up correctly
- set the password property to the alias with slower case key: ${alias=....}
- ping the connection. It fails due to authentication error.
- set the password property to the alias with upper case key: ${ALIAS=...}
- ping the connection. It works.
Operating System
Ubuntu 24.04.4 LTS
JDK Version
openjdk 21.0.11 2026-04-21
Payara Distribution
Payara Server Full Profile
Brief Summary
The Domain Admin Console describes the usage of password aliases in lower case notation:
To get it working for JDBC Connection Pool passwords, the notation of the key must be upper case:
Expected Outcome
JDBC connection pool ping should succeed, if the password property uses a password alias as described in the Domain Admin Console.
Current Outcome
JDBC connection pool ping fails due to authentication error, if the descibed lower case notation ${alias=....} is used. Connection ping succeeds if upper case notation ${ALIAS=...} is used.
Reproducer
This can be reproduced by:
Operating System
Ubuntu 24.04.4 LTS
JDK Version
openjdk 21.0.11 2026-04-21
Payara Distribution
Payara Server Full Profile