RapidIdentity Product Guides - 2019 Rolling Release

General

Settings_People.png
Table 359. People Settings Fields

Field Name

Description

Invalid Challenge Set Message

This message appears to users when they have an invalid challenge set. It is recommended to include contact information for your help desk in this message. The most common use of this message is when users are trying to use the Forgot My Password application but do not have a valid set of challenge questions for the application to use.

Enable Challenge Questions

Enables the API for setting challenge questions.

Enable Forgotten Password Retrieval

Enables the API for retrieving passwords by answering challenge questions.

Enable Forgotten Password CAPTCHA

Enables the CAPTCHA system for forgotten password retrieval.

Enable Forgotten Username Retrieval

Enables the API for retrieving usernames by providing the associated email address.

Enable Forgotten Username CAPTCHA

Enables the CAPTCHA system for forgotten username retrieval.

Enable Claim Account CAPTCHA

Enables the CAPTCHA system for the claim account process.

Selecting any of the CAPTCHA options requires administrators to enter a Site and Secret Key, as described in the Google Apps reCAPTCHA .

Enable Wildcard (*) Searches

Enables the use of searches with a wildcard “*”. These searches may cause extreme load on the RapidIdentity Portal server and the LDAP server. Wildcard searches should only be used in environments with small user bases and with appropriate LDAP indexes.

Show 'Show All' Checkbox In Delegations

Enables a 'Show All' checkbox in each delegation. This option should only be used when delegations only contain upwards of a few thousand users. Extremely large delegations can cause extreme load on the RapidIdentity Portal or LDAP server.

Access Control

Can be one of three types: None; Role-based; or Attribute-based.

Selecting either Role-based or Attribute-based triggers fields to define roles or attributes to determine the user population that can access the application.

Role-based allows administrators to define roles to include users matching that DN of the role. Attribute-based allows users matching the LDAP filter to access the application.