Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

1 Configuring and Diagnosing
Windows Application Templates

• 1.1 Overview of a Sign-On Event
• 1.2 Understanding Window Detection
  • 1.2.1 Detection of Java, SAP, and Windows 8 Metro Applications
• 1.3 Understanding Form Response
  • 1.3.1 Supported Form Types
  • 1.3.2 Supported Form Response Methods
    • 1.3.2.1 Control IDs
    • 1.3.2.2 "SendKeys"
    • 1.3.2.3 Control IDs with "SendKeys"
• 1.4 Determining the Optimal Configuration for a Form
  • 1.4.1 Determining the Optimal Configuration for a Logon Form
    • 1.4.1.1 Non-unique target window?
    • 1.4.1.2 Target window title blank or dynamic?
    • 1.4.1.3 Target window class dynamic?
    • 1.4.1.4 Target fields and controls appear in the Form Wizard?
    • 1.4.1.5 Non-unique or dynamic Control IDs in the form?
  • 1.4.2 Determining the Optimal Configuration for a Password Change Form
    • 1.4.2.1 Logon and password change forms on the same screen?
    • 1.4.2.2 Password change form on a tab different than logon form?
    • 1.4.2.3 Action required to initiate password change?
    • 1.4.2.4 Non-unique target window?
    • 1.4.2.5 Target window title blank or dynamic?
    • 1.4.2.6 Target window class dynamic?
    • 1.4.2.7 Target fields and controls appear in the Form Wizard?
    • 1.4.2.8 Non-unique or dynamic Control IDs in the form?
    • 1.4.2.9 Application requires confirmation of new password?
    • 1.4.2.10 Application displays a password change success and/or failure dialogs?
• 1.5 Configuring a Form
  • 1.5.1 Configuring a Form Using Control IDs
  • 1.5.2 Configuring a Form Using "SendKeys"
  • 1.5.3 Configuring a Form Using MS UIA (User Interface Automation)
  • 1.5.4 Using Matching to Improve Response Accuracy
    • 1.5.4.1 Matching for a Blank or Dynamic Value
    • 1.5.4.2 Matching Against a Window Title
    • 1.5.4.3 Matching Against a Window Class
    • 1.5.4.4 Matching Against an Executable Name
    • 1.5.4.5 Matching Against a Field, Control, or Text String
  • 1.5.5 Configuring an Application as a Service Logon
  • 1.5.6 Disabling Automatic "SendKeys" Fallback
• 1.6 Testing the Configuration of a Form
  • 1.6.1 Testing the Configuration of a Logon Form
    • 1.6.1.1 Agent detects window?
    • 1.6.1.2 Agent injects credentials?
    • 1.6.1.3 Logon loop occurring on logout?
    • 1.6.1.4 Agent responding properly after application is restarted?
  • 1.6.2 Testing the Configuration of a Password Change Form
    • 1.6.2.1 Agent detects the window?
    • 1.6.2.2 Agent injects and submits credentials?
    • 1.6.2.3 New password satisfies application's password policy?
    • 1.6.2.4 Agent responds to password change form as if it were a logon?
• 1.7 Publishing a Template to the Repository
• 1.8 Troubleshooting Window Detection
  • 1.8.1 Agent detects the window?
  • 1.8.2 Agent responds to target window but also to other windows?
  • 1.8.3 Agent detects window when using the "Logon Using Logon Manager" tray icon option?
  • 1.8.4 Application running as a service or a user other than the current?
  • 1.8.5 Window title changes after detection?
• 1.9 Troubleshooting Form Response When Using Control IDs
  • 1.9.1 Agent populates fields but does not submit the logon?
  • 1.9.2 Application rejects injected credentials?
  • 1.9.3 Fields populated erratically?
• 1.10 Troubleshooting Form Response When Using "SendKeys"
  • 1.10.1 Pre-filled fields cause erroneous logon?
  • 1.10.2 Cursor always starts in the same field and retains focus?
  • 1.10.3 Multiple values injected into a single field?
  • 1.10.4 Switching to "SendKeys" with journal hooks restores reliable injection?
  • 1.10.5 Characters missing from injected values?
  • 1.10.6 Using mouse click actions to focus on fields results in successful logon?
• 1.11 Troubleshooting Matching
  • 1.11.1 Target field or control recognized by Control Match Wizard?
  • 1.11.2 Non-unique or dynamic Control IDs in the form?
• 1.12 Troubleshooting a Logon Loop
  • 1.12.1 Post-logout form different from standard logon form?
  • 1.12.2 Configuring the "Logon Loop Grace Period" option resolves logon loop?
• 1.13 Troubleshooting Java Application Issues
  • 1.13.1 Installed JRE is a supported brand and version?
  • 1.13.2 Using Oracle JInitiator or another JRE not made by Oracle or IBM?
  • 1.13.3 JHO loaded?
  • 1.13.4 Verifying and Repairing the Permissions Required by the JHO
    • 1.13.4.1 Verifying That the Required Permissions Are Being Granted
    • 1.13.4.2 Restoring the Missing JHO Permissions
  • 1.13.5 Configuring the Behavior of the Java Helper Object (JHO)
    • 1.13.5.1 Manually Restricting the JHO to Specific JREs
    • 1.13.5.2 Manually Customizing the Event Response Behavior of the Java Helper Object (JHO)

2 Configuring and Diagnosing
Web Application Templates

• 2.1 Overview of a Sign-On Event
• 2.2 Understanding Web Form Detection
  • 2.2.1 Supported Form Types
  • 2.2.2 Understanding URL Detection
    • 2.2.2.1 Understanding URL Matching Precision
    • 2.2.2.2 Obtaining the URL of a Page, Element, or Pop-Up
  • 2.2.3 Understanding Field Detection
    • 2.2.3.1 Understanding HTML Elements
    • 2.2.3.2 Understanding the Frame Element
    • 2.2.3.3 Understanding the Form Element
    • 2.2.3.4 Understanding the Input Elements Supported by Logon Manager
  • 2.2.4 Recommended Page Inspection Tools
    • 2.2.4.1 DOM Inspector for Mozilla Firefox
    • 2.2.4.2 Firebug for Mozilla Firefox
  • 2.2.5 Understanding Detection Matching
    • 2.2.5.1 Detection Matching vs. Offset Matching
    • 2.2.5.2 Matching Against Text on the Page
    • 2.2.5.3 Matching Against HTML Code in the Page's Source
    • 2.2.5.4 Matching Against Names and Values of Element Attributes
    • 2.2.5.5 Constructing Complex Rule Chains Using Logic Operators
  • 2.2.6 Using Wildcards to Configure Detection Criteria
  • 2.2.7 Using Regular Expressions to Configure Detection Criteria
• 2.3 Understanding Form Response
  • 2.3.1 Control IDs
  • 2.3.2 "SendKeys"
  • 2.3.3 Control IDs with "SendKeys"
• 2.4 Determining the Optimal Configuration for a Form
  • 2.4.1 Determining the Optimal Configuration for a Logon Form
    • 2.4.1.1 Target fields and controls appear in the Web Form Wizard?
    • 2.4.1.2 Non-unique or dynamic field names?
    • 2.4.1.3 Dynamic page or element URL?
    • 2.4.1.4 Logon form is a Flash applet?
    • 2.4.1.5 "Submit" control is an image?
    • 2.4.1.6 Other fields on the page besides target fields?
    • 2.4.1.7 Application displays a logon success and/or failure message?
  • 2.4.2 Determining the Optimal Configuration for a Password Change Form
    • 2.4.2.1 Logon and password change forms on the same screen?
    • 2.4.2.2 Action required to initiate password change?
    • 2.4.2.3 Target fields and controls appear in the Web Form Wizard?
    • 2.4.2.4 Application requires confirmation of new password?
    • 2.4.2.5 Need to inject the same data into more than one field?
    • 2.4.2.6 Application displays a password change success and/or failure message?
    • 2.4.2.7 Non-unique or dynamic field names?
    • 2.4.2.8 Dynamic page or element URL?
    • 2.4.2.9 "Submit" control is an image?
    • 2.4.2.10 Other fields on the page besides target fields?
• 2.5 Configuring a Form
  • 2.5.1 Basic Configuration
  • 2.5.2 Manually Configuring a Field or Control
    • 2.5.2.1 Configuring a Field or Control Using the "Control IDs" Method
    • 2.5.2.2 Configuring a Field or Control Using the "SendKeys" Method
  • 2.5.3 Configuring URL Detection Criteria
  • 2.5.4 Configuring Additional Field Detection Criteria
• 2.6 Testing the Configuration of a Form
  • 2.6.1 Testing the Configuration of a Logon Form
    • 2.6.1.1 Agent detects form?
    • 2.6.1.2 Agent injects credentials?
    • 2.6.1.3 Logon loop occurring on logout?
• 2.7 Testing the Configuration of a Password Change Form
  • 2.7.1 Agent detects the form?
  • 2.7.2 Agent injects and submits credentials?
  • 2.7.3 New password satisfies application's password policy?
  • 2.7.4 Agent responds to password change form as if it were a logon?
• 2.8 Publishing a Template to the Repository
• 2.9 Troubleshooting Web Form Detection
  • 2.9.1 "Logon Using Logon Manager" tray icon option results in successful detection?
  • 2.9.2 Page completed loading?
  • 2.9.3 Is the appropriate helper object running?
  • 2.9.4 Removing all detection and offset matching rules results in successful detection?
  • 2.9.5 Truncating URL definition to host.domain form results in successful detection?
• 2.10 Troubleshooting Form Response when Using Control IDs
  • 2.10.1 Agent detects the form?
  • 2.10.2 Agent injects credentials but does not submit them?
  • 2.10.3 Fields populated erratically?
• 2.11 Troubleshooting Form Response When Using "SendKeys"
  • 2.11.1 Pre-filled fields cause erroneous logon?
  • 2.11.2 Cursor always starts in the same field and retains focus?
  • 2.11.3 Multiple values injected into a single field?
  • 2.11.4 Switching to "SendKeys" with journal hooks restores reliable injection?
  • 2.11.5 Characters missing from injected values?
  • 2.11.6 Using mouse click actions to focus on fields results in successful logon?
• 2.12 Troubleshooting Detection Matching
  • 2.12.1 Removing all matching rules restores form detection?
• 2.13 Troubleshooting a Logon Loop
  • 2.13.1 Post-logout form URL from standard logon form URL?
  • 2.13.2 Post-logout form different from standard logon form?
  • 2.13.3 Configuring the "Logon Loop Grace Period" option resolves logon loop?
• 2.14 Troubleshooting Java Application Issues
  • 2.14.1 Installed JRE is a supported brand and version?
  • 2.14.2 Using Oracle JInitiator or another JRE not made by Oracle or IBM?
  • 2.14.3 JHO loaded?
  • 2.14.4 Verifying and Repairing the Permissions Required by the JHO
    • 2.14.4.1 Verifying That the Required Permissions Are Being Granted
    • 2.14.4.2 Restoring the Missing JHO Permissions
  • 2.14.5 Configuring the Behavior of the Java Helper Object (JHO)
    • 2.14.5.1 Manually Restricting the JHO to Specific JREs
    • 2.14.5.2 Manually Customizing the Event Response Behavior of the Java Helper Object (JHO)

3 Configuring and Diagnosing
Mainframe Application Templates

• 3.1 Overview of a Sign-On Event
• 3.2 Understanding Form Detection and Response
  • 3.2.1 Fixed Screen Forms vs. Scrolling Screen Forms
  • 3.2.2 Supported Form Types
  • 3.2.3 Supported Credential Injection Methods
• 3.3 Determining the Optimal Configuration for a Form
  • 3.3.1 Determining the Optimal Configuration for a Logon Form
    • 3.3.1.1 Emulator supported by Logon Manager out of the box?
    • 3.3.1.2 Is the emulator HLLAPI-compliant?
    • 3.3.1.3 Is the emulator's HLLAPI implementation up to date?
    • 3.3.1.4 Non-unique target form?
    • 3.3.1.5 Logon form comprised of multiple screens?
    • 3.3.1.6 Logon and password change (PWC) forms on the same screen?
  • 3.3.2 Determining the Optimal Configuration for a Password Change Form
    • 3.3.2.1 Logon and password change (PWC) forms on the same screen?
    • 3.3.2.2 PWC form comprised of multiple screens?
    • 3.3.2.3 One or more non-unique screens?
    • 3.3.2.4 Application requests confirmation of new password?
    • 3.3.2.5 Application displays a password change success or failure message?
• 3.4 Configuring a Form
  • 3.4.1 Basic Configuration of a Fixed-Screen Form
  • 3.4.2 Basic Configuration of a Scrolling-Screen Form
  • 3.4.3 Advanced Form Configuration
    • 3.4.3.1 Defining Window Title Matching Rules
    • 3.4.3.2 Defining Additional Text Matching Rules
    • 3.4.3.3 Defining Additional Fields
    • 3.4.3.4 Adding Keystrokes, Pauses, or Text to the Logon Sequence
    • 3.4.3.5 Configuring a Form for Dynamic Column Positioning (Scrolling-Screen Only)
    • 3.4.3.6 Reducing Injection Speed
    • 3.4.3.7 Adjusting the Emulator Polling Interval
    • 3.4.3.8 Adjusting the Credential Request Delay Interval
• 3.5 Testing the Configuration of a Form
  • 3.5.1 Testing the Configuration of a Logon Form
    • 3.5.1.1 Agent detects the form?
    • 3.5.1.2 Agent injects credentials?
    • 3.5.1.3 Logon loop occurring on logout?
    • 3.5.1.4 Logon failure or expired password exceptions accounted for in the template?
  • 3.5.2 Testing the Configuration of a Password Change Form
    • 3.5.2.1 Agent detects the form?
    • 3.5.2.2 Agent injects and submits credentials?
    • 3.5.2.3 New password satisfies application's password policy?
    • 3.5.2.4 Agent responds to password change form as if it were a logon?
• 3.6 Publishing a Template to the Repository
• 3.7 Viewing and Modifying Emulator Configuration
  • 3.7.1 Emulator Configuration Parameter Reference
• 3.8 Troubleshooting Form Detection
  • 3.8.1 Agent detects the form when invoking the "Logon Using Logon Manager" tray icon option?
  • 3.8.2 Valid entry for the emulator exists in mfrmlist.ini?
  • 3.8.3 Has "Host/Mainframe Support" global Agent setting been disabled?
  • 3.8.4 Match text, field text, and corresponding coordinates correct?
  • 3.8.5 Emulator's HLLAPI implementation up to date and enabled?
  • 3.8.6 Appropriate mainframe support component installed?
• 3.9 Troubleshooting Form Response
  • 3.9.1 Agent detects the form?
  • 3.9.2 Agent injects credentials but does not submit them?
  • 3.9.3 Enter keystroke explicitly added to the logon sequence?
  • 3.9.4 Fields populated erratically?
• 3.10 Troubleshooting a Logon Loop
  • 3.10.1 Post-logout form different from standard logon form?
  • 3.10.2 Configuring the "Logon Loop Grace Period" option resolves logon loop?
• 3.11 Troubleshooting Detection and Response with the SSO MHO Status Tool
  • 3.11.1 Understanding the MHO Status Tool Interface
  • 3.11.2 Using the MHO Status Tool to Diagnose Session Detection and Response