Enterprise SSO opens the change password window when it detects that an application has requested a password change. This request can be triggered by one of the following actors:
The window prompts the user to register a new password for the application.
When this feature is activated, Enterprise SSO looks for definitions of supported window types in HTML files.
When, during an interaction with the user, Enterprise SSO cannot find or cannot read the appropriate file, or if the contents of the file do not meet Enterprise SSO requirements (see Organizing the Content of the files), Enterprise SSO uses the appropriate standard window instead, as if the customization feature were not activated.
The customization is activated.
NOTE: To deactivate customization, set the value to 0.
When the customization feature is activated, Enterprise SSO tries to load window definition files from a directory on the local hard disk.
By default, Enterprise SSO tries to load files from its current working directory, i.e. the directory in which Enterprise SSO is installed. However the directory can be specified explicitly by creating a new string value, called HtmlDialogDirectory, in the Windows Registry. This value can be set under the same keys as the UseHtmlSSODialogs value: see the Procedure in Activating the Customization.
If you set this value, it must be the full path name of a directory on the workstation's local hard disk.
The default file names used by Enterprise SSO for the three interactions described in SSO Window/Interaction Types are the following:
However, each time one of these interactions occurs, it occurs in the context of a particular managed application.
If a file exists and its name starts with the name of the E-SSO application object, continues with a '-' character and ends with the default file name; this file is used to define the window for the interaction. That is, if Enterprise SSO manages a user's access to an application called Supply Management, it tries to load a file called Supply Management-NewAccount.html when collecting the user name and password from the user.
If this file does not exist, Enterprise SSO tries to load a file called NewAccount.html. This means that it is possible, for example, to have two files for password-change interactions: a file called
Supply Management-ChangePassword.html to be used to change passwords in the Supply Management application and the ChangePassword.html file to be used to change passwords in all other applications.