Current Behavior

The clientAlias filled with the name of the authAlias throws an error about clientAlias or clientId/clientSecret being required. I did doublecheck if the authAlias was resolvable elsewhere. Workaround was to try and use clientId=${<aliasName>/username} and clientSecret=${<aliasName>/password}. I forgot what the exact error was, but I believe it was the same error as the one thrown by clientAlias. Only hardcoding the clientId and secret seems to work

Expected Behavior

clientAlias should resolve to given authAlias. ClientId and clientSecret should be able to expand properties/authAlias reference.

Environment Information

FF! 9.2.0-20250416.042336: Frank2Eekels 1.0.0
Running on 9f38f0f7d4f6 using Apache Tomcat/10.1.40
Java Version: OpenJDK Runtime Environment (21.0.6+7-LTS)
Heap size: 242.5 MiB, total JVM memory: 336.0 MiB
Free memory: 93.5 MiB, max memory: 3.8 GiB
Free disk space: 980.1 GiB, total disk space: 1006.9 GiB
Up since: 2025-04-17 09:45:55, timezone: Europe/Amsterdam

Steps To Reproduce

No response

Configuration

Input

No response

What database are you using?

No response

What browsers are you seeing the problem on?

No response

Relevant Log Output

Anything else?

No response