Unexpected user login request after having configured to use Single Sign-On

It might happen that, after running successfully all the steps required to configure the Single Sign-On between the Dynamic Workload Console and a IBM Workload Scheduler engine, when you try to test the connection or run a task on that engine, you are unexpectedly prompted to enter your user credentials to connect. This behavior means that the Single Sign-On method is not working properly on that engine and you receive the following exception:

Cause and solution:

Locate the authentication_config.xml configuration files on both the Dynamic Workload Console and the master domain manager.

The file is located in the following path for the master domain manager:

On UNIX operating systems: TWA_DATA_DIR/usr/servers/engineServer/configDropins/overrides
On Windows operating systems: TWA_home\usr\servers\engineServer\configDropins\overrides

The file is located in the following path for the Dynamic Workload Console:

On UNIX operating systems: DWC_DATA_dir/usr/servers/dwcServer/configDropins/overrides
On Windows operating systems: DWC_home\usr\servers\dwcServer\configDropins\overrides

Make sure that the files have identical values assigned to the name field of the primaryRealm section. This setting belongs to the WebSphere Application Server Liberty Base profile configuration.

For example, even though you ran all the required steps to configure the Single Sign-On, it might still not work if you set name="myHost.myDomain:389" on the Dynamic Workload Console and name="myHost:389" on the IBM Workload Scheduler engine. To make it work, you must enter: name="myLDAPHost.myDomain:389".