RapidIdentity Product Guide: Legacy UI

Plugin Configuration

The Plugin Configuration tab allows administrators to configure an application to use the RapidIdentity Browser Plug-in. It is necessary to install the browser plugin in order for this application to work properly.  

Legacy_Plugin_Configuration.png

This configuration is available when administrators select HTTP Basic and Form Fill Authentication (via Plugin) as the Type in the General tab.

The exact steps necessary to configure the authentication vary based on how the service provider has their authentication process configured. As a representative example, form fill to Gmail is shown.

  1. Navigate to Applications & Categories | Applications and click the green plus sign to create a new application definition.

  2. Click Create Custom App Definition.

  3. Complete the required fields in the General tab and then select Form Fill Authentication (via Plugin) as the Type.

  4. Navigate to the Plugin Configuration tab.

  5. Gmail's process requires two steps: enter the Email address on the first page and then the password on the next page. Administrators can complete the first step in the fields listed and then click Add Login Step or click Add Login Step first and then complete the fields for each step in any sequence desired. For service providers requiring more than two steps, click the green plus sign to add additional authentication steps. 

    Legacy_Plugin_Config_-_Step_1.png
    Legacy_Plugin_Config_-_Step_2.png
Table 252. Plugin Configuration Fields

Field

Description

Step Name

An arbitrary name for the step (e.g. Step 1, Enter Username)

Page URL Matching

The URL for which information will be form filled in the step. Wildcard (*) URLs are supported (e.g. https://www.example.com/*)

Page Title Matching

The name of the URL page (e.g. Gmail). If a wildcard URL was listed in Page URL Matching, this field should be an asterisk.

Match Attempts

The number of attempts the browser plugin should attempt to complete the form.

Retry Interval (seconds)

The time interval for the browser to "wait" before attempting to match the Page Elements for each Match Attempt.

Page Elements

Page Elements include the fields, buttons, and checkboxes that must be completed to authenticate successfully. Adding a page element opens a modal to allow administrators to name and find the element on the page using one of six options and also to determine whether the element is required.

  1. ID

  2. Name

  3. Class

  4. Text

  5. XPath

  6. Selector

The modal also allows administrators to select one of six actions to be performed on the page elements

  1. Text

  2. Password

  3. Click

  4. Checkbox

  5. Delay

  6. Enable

  7. Select

When selecting Password, the characters are masked initially, however, administrators can view the password only during its initial configuration by clicking the Show checkbox. Once the configuration is saved, the password never displays in the UI and its value is encrypted in the database. Application administrators can update the password if desired. If the Application definition is exported and then subsequently imported, it will be necessary to update the password since the encrypted password is not exported.

Selecting the proper action

It is important to select the correct action when working with passwords. When the "Password" action is selected, tokenized values are not supported and the password is encrypted in the database. Thus, the "Password" action is best for hard-coded passwords.

If a password is not intended to be hard-coded and is intended to be tokenized, select the "Text" action and use the expression %session.password%.

Note

A Password Filter is required to use %session.password% with form fill or any other function.



   6.      Complete each of the fields as shown. 

Legacy_Enter_Username.png
Legacy_Enter_Password.png

   7.      Click Save.