What is the Window Finder and what is it used for?

  • 7940229
  • 19-Aug-2009
  • 16-Jan-2014


SecureLogin SSO
All Versions



What is the Window Finder and what is it used for?



In addition to the predefined application definitions and the powerful wizards, to SSO enable or customize applications, SecureLogin includes a Window Finder tool that gives you X-Ray vision to an application. It allows you to interrogate what Windows application developers have assigned as the Title, Class, Dialog IDs etc. It also displays the executable name and command line. This information can be used to develop a fully functional script.

The Window Finder is installed when you install the SecureLogin client and an icon is added to the SecureLogin program group. Wintool.exe runs the Window Finder.

To inspect an item on a message box, dialog box or other window, right click on the icon in the middle of the Window Finder and drag and drop it on the item in question (e.g. Title bar, Username field, OK button, Error Message etc.) The Window Finder will then display the details of the control.

The following screen shot displays the results of the window finder after the Username field within a test application is highlighted. It shows the relationship between the Username and the Title.

Note: When you highlight the Username and Password fields, the Window Title should be the title of the application’s logon screen. If it isn’t, you may have to use the Parent command as per the knowledgebase article on the Parent command.

The Title is ""Login"", the Class is #32770 and the Username field is #1001. From the window finder the SSO administrator could easily develop an application definition to enter the Username into the appropriate field using the following lines. They could then use the window finder to view other field IDs and fully enable the application for password entry, to click OK, handle error messages etc.

# Logon Prompt # 
Dialog Title ""Login"" 
Class #32770 
Type $Username #1001 
Type $Password #1002 
Click #1

The information displayed is as follows;

Module Details:

Module Name

This is the name of the executable that ""owns"" the window.

This is the name that you will need to use for the platform

name of the windows Single Sign-on script.

Command Line

This is the command line of the executable. It may include

switches, IP addresses and database names that can be read

to distinguish one application from another, even if they

have the same executable and logon prompt.

Parent Details:

Window Title

The title of the control’s parent. Used in a ""Title""


Window Class

The class of the control’s parent. Used in a ""Class""



The handle of the control’s parent. For information only.

Control Details:

Dialog ID

Each control has a unique identifier called the control ID

and it is represented numerically (e.g. #1 is often the OK

button whilst #2 is often the Cancel button).

Use this number as the target for ""Type"", ""Click"", ""Ctrl"",

""SetPlat"" and ""ReadText"" commands (for example).

Class Name

The class name of the control. Used in a ""Class"" statement.

Window Text

This field displays the text contained within the control. This can be useful in troubleshooting and for writing the regular expression required by the ""SetPlat"" command.


The handle of the control’s parent. For information only.

Note: If you are having trouble SSO enabling an application, you should drag and drop the Window Finder over the username and password fields to check their relationship with the window Title. If the title of the control’s parent is not the window title you can see, you may have to use the Parent command to SSO enable the application. Some username and password fields exist within frames, particularly with VB developed applications.