Occasionally the Citrix Password Manager Agent may not recognize or submit credentials to web applications. This issue stems from Password Manager initializing before the webpage is ready for input. To alleviate this issue, Password Manager has an "Agent Launcher Delay". This article will discuss how this delay can be manually set by using the registry on a per agent basis.
Technical Background:
When launching published applications, occasionally the SSOLauncher will prematurely determine that SSOShell and SSOBHO are ready. The SSOLauncher makes this determination using the FindWindow() function on SZ_WND_TRAY + SZ_WND_BHO_HOOK. In some cases this prevents the Password Manager Agent from submitting credentials to the published web applications launched by the user.
Configuring the Citrix Password Manger Agent Launcher Delay
To alleviate this issue, Password Manger has incorporated a registry setting that can be implemented manually. After setting the registry entry, the SSOLauncher will sleep a predetermined amount of time after detecting SZ_WND_TRAY and SZ_WND_BHO_HOOK. The default setting for this sleep interval is 0, but the interval can be customized with a new registry value "LauncherDelay". This value is a DWORD expressed in milliseconds.
To manually add LauncherDelay to the registry
- As an administrator launch regedit.exe and browse to:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\MetaFrame Password Manager\Shell\
- If the entry "LauncherDelay" does not exist, Create a new "DWORD Value" named "LauncherDelay" and set it to 1 or higher
Note: Some experimentation will need to be performed by the administrator until a proper timing is achieved.
