Article
Problem
SecureLogin takes too long to initialize on user login. Also, an automatically launched Internet Explorer session is not scanned if it is open before slproto.exe is initialized completely. If you use a User Policy package with a GPO to launch a portal, and you want to have SecureLogin sign in, there are no configuration changes to SSO that you can make.
Solution
I created an AutoIT script launched in the Logon attribute of the User GPO that accepts a single URL parameter. The AutoIT script waits for slproto.exe to exist for up to 10 seconds. Once it exists, the script waits 2 more seconds and then launches Internet Explorer with the URL passed in the launch command. SecureLogin is loaded completely, and the profiled application will then log in as directed by SecureLogin.
Example Script
#cs ---------------------------------------------------------------------------- AutoIt Version: 3.2.4.9 Author: Aaron.White@pisd.edu Shoutout to Marko and David. Script Function: Wait for SecureLogin (slproto.exe) to load and then launch iExplore to a link that is supplied dynamically when this application is called. #ce ---------------------------------------------------------------------------- $loopTimer = 0 Do Sleep(1000) $loopTimer = $loopTimer + 1 Until ProcessExists("slproto.exe") Or $loopTimer == 10 Sleep(2000) Run( "c:\program files\internet explorer\iexplore.exe " & $CMDLINE[1] )
Environment
- Windows XP Pro SP2
- SecureLogin 6.0.106
- Internet Explorer 6.x
- AutoIT 3.2.4.9
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3923 reads


0