RapidIdentity Product Guide: Legacy UI

Applications Tab

This list displays the name of each web-based application.

Applications can be created or removed by clicking the plus or minus buttons, respectively, however, applications can be disabled which will render them inactive without the need to delete the application. When the plus icon is clicked, administrators can choose to import an existing application from RapidIdentity Depot or create a custom application definition. An application imported from Depot can be modified as needed. 

To export an application definition, click the export button. To import an application definition, click the import button.

There are two currently supported import and export fields.

Legacy_Import_Export.png
Table 247. Import and Export Fields

Field

Description

Priority

Application URL

Application Access (all)

Type (all)

Form Submit Method (all)

Username (Basic Auth only)

Form onSubmit Javascript

Form Items (all)

Password (Basic Auth only)



Legacy_Applications.png
Table 248. Applications General Tab Fields

Field Name

Description

Name

Required. The name of the application as it will appear in RapidIdentity Portal.

Description

A description of the application. This information is only displayed here.

Type

The type of application authentication to use.

  • No authentication. This is typically used with federation/SSO provided the Service Provider is configured in RapidAppliance.

  • Form Fill Authentication: pass attributes to authenticate a user.

  • Send username and password in the URL field.

Application Access

Can be one of three types: Authenticated and Anonymous Users; Anonymous Users Only; or Authenticated Users Only

Status

Determines if the application icon link will be visible in RapidIdentity Portal.

Priority

Required. This value allows administrators to determine both the relative order and application icon size users see when accessing My Applications.

Assigning priority is very useful when users have access to large numbers of applications, particularly if accessing applications from a mobile device.

Applications can have equivalent priority (e.g. 3 applications set to priority 100).

Require Bookmark

When selected, this application displays in the user's Bookmarks in the Dashboard module.

Application Icon

Required. The application display icon. The application can use one of the built-in icons or a custom uploaded icon, where the optimal icon size is 64.64.

Custom Icons will load over HTTP. If HTTP (80) isn't open on the RapidIdentity Portal server or is redirected via a firewall or proxy, uploading may not work.

Background Color

Required. These color swatches are calculated automatically based on the colors in the selected application icon. Up to six color swatches will display and the leftmost color swatch is always white. If a color is not selected upon saving, the background color will be white. Once a color swatch is selected a concentric circle appears around that color. If a different color is desired beyond the color swatches preselected, click the box to the right of the color swatches to use the color picker or to type in the desired hex color code.

Application URL

Required. The application URL. Tokens may be used in the Application URL. All LDAP attributes are valid.

Owner

Required. The user responsible for this application.



Legacy_RBAC_ABAC.png
Table 249. ACLs Tab Fields

Field Name

Description

Enable RBAC

Enable/Disable Role Based Access Control.

Role(s)

Role DN for the role allowed to request resources in this category.

Role Exclusion ACL

Role DN of the group not allowed to request resources in this Category.

Enable ABAC

Enable/Disable Attribute Based Access Control.

Attribute ACL

The LDAP filter (e.g. (employeeType=Staff)). Only users who match the specific LDAP attribute(s) will have access to this application.



Legacy_Form_Submit.png
Table 250. Form Data Tab Fields

Field Name

Description

Form Name/ID

The name or ID in the HTML of the target form.

Form Submit Method

Match this to the target form. More information on Get and Post can be found here.

Form onSubmit Javascript

Javascript to run after the form has been filled. This is sometimes useful to get hard-to-fill applications working. For an onSubmit primer, click here.

Form Items

The required target form items. Simple forms may only require username and password. Others may require more information.



Legacy_Auth_Data.png
Table 251. Basic Auth Data Tab Fields

Field Name

Description

Form Submit Method

Match this to the target form. More information on Get and Post can be found here.

Username

The username value (tokens supported) to pass to the application as the username for basic authentication.

Password

The password value (tokens supported) to pass to the application as the username for basic authentication.

*Basic authentication via this module does not work with Internet Explorer. Users using Safari will also have their username and password exposed in the URL bar. If either of these is a concern for the environment, it is best to use the Form Fill Authentication and to create a custom form to submit the basic authentication. More information can be found here: http://stackoverflow.com/a/11960692/1723930.