Environment
NetIQ SecureLogin
NSL8.x
Novell SecureLoginNSL7SP2
Internet Explorer 8
Internet Explorer 11
Windows 7 workstation or newer
Outlook
.Net (aka dotnet) applications
Window Finder tool that ships with NSL7sp2
Outlook
.Net (aka dotnet) applications
Window Finder tool that ships with NSL7sp2
DotNet Window Finder tool that ships with NSL 8.x
Situation
IExplore.exe script does not act upon login prompt in “Windows Security" dialog.
Script created for iexplore.exe Security Window works fine on XP, fails on Win7.
Windows finder does not detect text on IE login screen with Windows 7 or newer.
Script created for iexplore.exe Security Window works fine on XP, fails on Win7.
Windows finder does not detect text on IE login screen with Windows 7 or newer.
Similar problems occur for other .Net applications.
Resolution
Create a .Net application definition for iExplore that responds to the login prompt.
In other words, in addition to any existing application definition for iexplore.exe,
create a new application for iexplore without the .exe extension. Define this as type "Windows," use the dotnet window finder to identify the desired fields and script manually.
Steps:
1. Right click on the NSL “Hand” icon on the workstation and select “Manage Logins.”
2. Right click on “Applications” and select “New."
3. Click on “New Application Definition” and then
- select “Windows” from the drop-down box for "Type."
- in the EXE box enter"iExplore" (without the .exe extension – just iexplore)
- enter a description that helps you remember that this is the .Net version of the iexplore script
4. Use the Dot NET Window Finder that ships with NSL7SP2 to identify the control fields for Username, Password, OK button, etc. The Dot NET Window Finder tool is found in the NSL7SP2 distribution files in the directory ... \SecureLogin\Tools\Unsupported\DotNet WindowFinder
5. Create a script similar to the following:
Dialog
Title "Windows Security"
EndDialog
Type $Username #4
Type $Password #5
Click #7
The key is to script .Net applications like Windows applications, but define them without the “.exe” extension. Dot net application definitions use the same commands and syntax as Windows application definitions. The difference is that Windows scripts recognize applications with their .exe file extension, and .Net application definitions recognize the application without any extension at all.
In other words, in addition to any existing application definition for iexplore.exe,
create a new application for iexplore without the .exe extension. Define this as type "Windows," use the dotnet window finder to identify the desired fields and script manually.
Steps:
1. Right click on the NSL “Hand” icon on the workstation and select “Manage Logins.”
2. Right click on “Applications” and select “New."
3. Click on “New Application Definition” and then
- select “Windows” from the drop-down box for "Type."
- in the EXE box enter"iExplore" (without the .exe extension – just iexplore)
- enter a description that helps you remember that this is the .Net version of the iexplore script
4. Use the Dot NET Window Finder that ships with NSL7SP2 to identify the control fields for Username, Password, OK button, etc. The Dot NET Window Finder tool is found in the NSL7SP2 distribution files in the directory ... \SecureLogin\Tools\Unsupported\DotNet WindowFinder
5. Create a script similar to the following:
Dialog
Title "Windows Security"
EndDialog
Type $Username #4
Type $Password #5
Click #7
The key is to script .Net applications like Windows applications, but define them without the “.exe” extension. Dot net application definitions use the same commands and syntax as Windows application definitions. The difference is that Windows scripts recognize applications with their .exe file extension, and .Net application definitions recognize the application without any extension at all.
Additional Information
Note that the he Credential provider in Windows Vista/2008/7 has changed and uses a non win32 toolset. Winsso sees the text as an image, which is why the standard Window file tool cannot identify the fields. The DotNetWindowFinder is able to identify the fields and read the text.