Customer is SSO enabling a web application running in Internet Explorer. Using MMC they published the application at CN=Users by creating a new application and naming it with the partial name of the web site they wish to SSO enable;
They expected the application definition to run when a URL with intranet.finance in the name appears, including intranet.finance/logon.htm, intranet.finance/changepassword.htm , intranet.finance/failedlogon.htm etc.
Everything was working when the application definition was associated directly against the user object, but now it has been published it simply isnât running. When the customer navigates to that site, nothing happens.
All other applications, including web applications, are logging on using SSO. SecureLogin is active and the application has not been specifically disabled.
The customer checked their syntax and it is fine. As part of their troubleshooting, they placed a line at the very top of the script to see if the script was being invoked;
MessageBox ""I can see this web script running""
When they launch the application nothing happens. The message box does not appear.
When the customer SSO enabled the application, they inadvertently created it as a Windows application type.
The customer copied the application definition to the clipboard and then deleted the application that had been setup as Windows type. They recreated it with the same name, as an Advanced Web application, and pasted it back in.
When they refreshed the cache on the SecureLogin client (to download the new application definition) SSO immediately operated as expected.