Recent Changes - Search:

Categories

Account Unlock

PortalGuard's Account Unlock Feature

Tags: Self Service Actions

Problem Definition

You have an installation of PortalGuard and your are interested in learning more about PortalGuard's account unlock feature.


Attach:AccountUnlock1.jpg Δ

Unlock Account - Allows users to unlock their account only. This does not change the user's current password.

Authentication Type Requirements - Controls if completing this action requires a single -OR- multiple/combined authentications (e.g. multi-factor).

Unlock Account Using Optional Challenge Answers - Verify identity by answering a subset of previously enrolled optional challenge questions.

Unlock Account Using Mandatory Challenge Answers Only - When optional challenge answers have NOT yet been enrolled by the user, allow them to verify their identity by answering only their mandatory challenge questions. This is most helpful for first-time users who had their mandatory answers batch imported. When both of these sub-options are unchecked, users must always answer mandatory -AND- optional questions to continue.

Unlock Account Using Optional Challenge Answers Only - Once a user has enrolled optional answers, allow them to verify their identity by answering only them (skipping mandatory questions). This is helpful if mandatory answers should only be used by new end-users who have mandatory answers batch imported. When both of these sub-options are unchecked, users must always answer mandatory -AND- optional questions to continue.

Accepted OTP Methods – The OTP types that are allowed to help prove the user’s identity for this action.

• Default OTP Type - Controls which of the enabled OTP methods will act as the default for this action. This affects the prompts the user will receive.

  • Example 1 - Phone OTP is chosen: An OTP is immediately sent to their phone when required.
  • Example 2 - YubiKey is chosen: No OTP is sent and the user is prompted to enter an OTP from their YubiKey.
Page last modified on March 11, 2016, at 12:56 PM