Product Documentation

Identifying Windows Forms with Advanced Matching

Feb 06, 2011

The Identify forms page of the Form Definition Wizard provides enough form identification matches for most Windows applications. Some user credential management forms require additional identifiers. For these forms, Single Sign-on offers Advanced Matching. You can access this feature from the Identify form page of the Form Definition Wizard by clicking Advanced Matching.

Advanced Matching offers five advanced identifiers for Windows applications:
  • Class Information
  • Control Matching
  • SAP Session Information
  • Window Identifier
  • Identification Extensions

Ignoring Forms Using Class Information

Using the Class Information page, you can identify forms you want Single Sign-on to ignore. If you type a Window class into the Ignore this window class field, the Single Sign-on Plug-in does not react when a form with that class information appears.

Do not use this type of matching for .NET applications or applications that use Windows class 32770 (default class).

This setting is useful when the Window class is dynamic. In this case, use wildcard characters to match a dynamic Windows class identifier.

Wildcard Description
? Use only for a single dynamic/changing character.
* Use this value to represent dynamic identifier data for one or more characters. This value is not recommended for empty Windows class identifiers. Use NULL for these situations.
NULL Use this value for empty Windows class identifiers (the word “NULL” must be all uppercase).
Use Windows class identifiers when trying to identify one Windows class from among many possible Windows class targets. The following conditions apply:
  • The specified window title and associated executable file result in multiple matching candidates. This condition most often occurs when the Windows title contains dynamic data and wild cards are specified.
  • The target form must be associated with a unique Window class identifier and all other candidates must use different Window class identifiers.

To identify class information

Start this procedure on the Identify form page of the Form Definition Wizard.

  1. Click Advanced Matching and then select the Class Information option.
  2. Click Select to choose the target application from among the applications currently open on your computer.
    Note: To expand your choices, select the Show hidden program windows check box or the Show child windows check box.

Defining Matching Criteria With Control Matching When Associated Identifiers are Identical

Some applications assign dynamic information to control labels. In these cases, the window title, its associated executable application, and the control ID (or IDs) can be the same for several different user credential management forms while the text labels or other properties on the form change in response to application-specific events.

For these types of forms, use the control matching configuration options to uniquely identify a form for a specific plug-in action based on the unique class, style, or text values associated with control ID (or multiple control IDs if multiple definitions are required to uniquely identify the form).

To define matching criteria

Start this procedure on the Identify form page of the Form Definition Wizard.

  1. Click Advanced Matching and then select the Control Matching option.
  2. Click Add Match.
    Note: Define only enough control matching criteria to uniquely identify the user credential management form being defined.
  3. From the Define Matching Criteria dialog box, click Select.
  4. Right-click a control ID entry.
  5. Select Class, Style, or Text to choose a characteristic to be used to qualify the form for the selected control ID.
  6. Repeat Steps 4 and 5 for each control ID that is to be used to uniquely identify the form.

Identifying Matches When Using Multiple SAP Sessions

Older versions of SAP are managed using the standard Windows and Web application definitions. However, the Advanced Matching dialog box provides support for SAP applications when multiple SAP systems are defined to use the same SAP GUI user logon interface (such as SAP Logon Pad).

SAP Session Information support requires that the SAP administrator enable GUI scripting on the server. This allows the console and Single Sign-on Plug-in to interrogate the SAP Logon Pad and determine the System ID or Server name (or both) required to uniquely identify the specific user credential management form.

By using the SAP Session Information option, the session information can be extracted from an SAP window to uniquely identify and differentiate one SAP logon window from another.

To manually define SAP session information

The SAP System ID and Server Name field values can be manually entered. Both fields accept regular expressions for their respective values. This is useful for controlling the ability to match multiple servers.

You may also want to manually enter the values to match DNS and NetBIOS names of a server.

Use the following regular expression format to support both DNS and NetBIOS.

^servername(\.domain\.com)?$

To generate an SAP GUI scripting message

SAP GUI scripting messages can be generated whenever a program attempts to establish a connection to the SAP LogonPad using the SAP GUI. In this case, a registry setting can be changed to prevent the message.

The key is HKEY_CURRENT_USER\Software\SAP\SAPGUI Front\SAP Frontend Server\Security\WarnOnAttach. It is a DWORD. If this key value is set to 0, a message is not shown. The default value is 1.