ESSO diagnostic mode allows users of ESSO engine to see why the SSO does not work on an application and to dynamically modify the configuration to adapt it.
Note: test mode does not allow saving the modification
1. An application can be tested only if test mode has been authorized on the application profile. When test mode is allowed for an application, users can start a test tool for it. From the ESSO Console, Activate the "Allow the user to test the application with SSOWatch" or "Allow the user to test the application with Enterprise SSO" option in the relevant application profile (Typically "Default application profile)
2. From SSOWatch select the "Refresh" button. Right click in the application list, and ensure "Hide Application without credential" is unticked.
When diagnostic mode is allowed for an application, the user can right-click on the application from SSOWatch and select “Test application…” to start the test tool. This test tool must be launched before the application to detect. When the test tool is started, all SSO actions are blocked except the one currently tested.
When the test tool is closed the ESSO Engine can perform standard SSO again.
3. The user must specify which SSO window they want to test. In test mode, a “bad password” configuration or a “new password” configuration can be tested without having performed an initial login with SSOWatch.
The “Window configuration information” panel indicates the elements to be detected.
The “Live report” panel shows the current status of the SSO.
4. A sample web application
5. A Win32 application
“Advanced detection failed”: shows found/expected values
If the test failed, then the defined constraint value and the evaluated value are indicated in the report.
Note: when you test a “bad password” configuration or a “new password” configuration, user must collect the account and then give the (new) password.