• No results found

Usually the best (and simplest) way to gather the information required for Web application definitions is to launch the application and navigate to the form that requires a user credential management event (user logon, change password, successful password change, or failed password change) while running the Form Definition wizard from the console or from the Application Definition Tool. The wizard’s on-screen text provides instructions for locating and identifying the applicable parts of the application.

Form Definition Process

The form definition process consists of collecting the form-specific identification information, and action information using the following pages in the Form Definition wizard for Web applications:

• Name form

• Identify form

• Configure other settings

• Confirm settings

After completing the actions required for a specific page, click Next to proceed through the wizard. The Back button is generally available on each page to return to some previously configured options. However, changing some previously configured options may require you to alter subsequent settings.

Name Form

When creating application definitions for Web type applications, the Name form page of the Form Definition wizard is used to:

• Assign a user-defined name to the form being created

• Identify the type of form being created

• Identify any special actions

Consider that the name assigned to the form appears on the Manage forms page of the Application Definition wizard. Assign a name that is meaningful to the type of form being defined.

Several types of standard user credential processing forms can be defined using the Form Definition wizard including:

Logon form

Used to identify the logon interface to an application, and to manage the user credential actions required to gain access to the associated application.

Password change form

Used to identify the password change interface to an application, and to manage the user credential actions required to change the user password to the associated application.

Successful password change form

Used to identify the password change interface to an application, and to manage the user credential actions required to acknowledge the successful change to a password for the associated application.

Failed password change form

Used to identify the unsuccessful password change interface to an application, and to define the actions to take when a credential change operation is unsuccessful.

Password Manager Agent Versions 4.0 and 4.1 do not support successful or failed change credentials forms and do not respond to application definitions containing these forms.

Use the Special actions area to identify any special form treatments for the form being defined:

No special action

Select this option for normal Web form processing.

Redirect to Windows application

Select this option when no form is recognized for the web application in the Web Form wizard (see “Identify Form”). This occurs when the Web application uses ActiveX controls, Flash-based controls, some types of Ajax controls, or other non-HTML based controls used to manage user credential management events. See “Redirect to Windows Application Configuration” on page 67 for additional configuration information.

Ignore this form when it is detected by the agent software Select this option to have the agent software ignore the form.

Identify Form

When creating application definitions for Web type applications, the Identify form page is used to provide the information required to have the Password Manager Agent software uniquely recognize the form being defined.

Web applications are identified using the URL address associated with the user credential management form being defined.

Click Select to open the Web Form wizard that is used to identify the URL address and define the user credential management actions for the form being defined (see “Web Form Wizard” on page 67).

After completing the Web Form wizard, you are returned to this page. Two check boxes are available to manage how to interpret identified URLs:

• Strict URL matching

Select this check box to recognize only user credential management events from Web applications that are started using the specified URL(s). Some URLs may contain dynamic data such as session management identifiers, application parameters, or other identifiers that can change for each instance. In these circumstances, using strict matching results in the URL to not be recognized.

• Case-sensitive URL

Select this check box to use exact case matching URL(s).

Configure Other Settings

For Web definitions, this page is used to specify if the submit button is

automatically pressed by the agent software or if the user is required to manually press the button.

Select the Agent submits this form automatically check box to automatically submit the form without user intervention.

Some Web applications use dynamic URLs. If this condition is encountered, click Advanced to access the Advanced Settings dialog box that is used to specify additional form definition criteria to match the Web form (see “Advanced Settings Dialog Box for Web Applications” on page 68 for additional information).

Confirm Settings

The Confirm settings page is the last page of the Forms Definition wizard. It is used to review the configuration options and settings associated with the form. It allows the administrator to review the configuration before finishing the form and returning to the Application Definition wizard to define additional forms or to complete an application definition editing task.

Related documents