Unique ID for this flow, which is used for selecting or referencing a flow.

Flow ID

Steps of the flow.

Abort Step Acknowledge Message Step Airlock 2FA Activation Step Email Notification Step Email Verification Step Failure Step No Operation Step OATH OTP Activation Step Phone Number Verification Step Realm Assignment Step Red Flag Raising Step SSI Self-Registration Issuance Step SSI Verification Step Scriptable Step Selection Step for User Self-Registration Send Email Link Step Set Authentication Method Migration Step Set Authentication Method Step Set Context Data Step Tag Removal Step Terms Of Services Step User Data Registration Step User Persisting Step User Role Assignment Step User Unlock Step (Self-Registration) Username Generation Step

List of additional user data items whose global uniqueness is enforced by the system. Note that all login names (username and alias names) are automatically considered for the uniqueness verification.

String User Context Data Item

The lock reason used for initially locking the self-registered user.

At the start of the flow the user is initially locked and a User Unlock Step is needed to unlock it.

LockReason.AwaitingAdminApproval

LockReason.PendingChannelVerification, LockReason.AwaitingAdminApproval

The password repository used to persist passwords. Required if there is a data registration step with a "Password User Item" configured.

The "Default Password Repository" cannot be used here.

Active Directory Password Repository Default End-To-End Encryption Password Repository Default Password Repository External Database Password Repository LDAP Password Repository RADIUS Password Repository Selection Password Repository

If enabled, the next authentication flow after completing this self-registration flow will be initialized with the user identity and tags from the self-registration. By combining this feature with authentication flows where steps can be skipped based on tags from self-registration, a non-interactive authentication after completed self-registration can be achieved.

false

Determines whether the registration should run in Stealth Mode, which can protect against enumeration attacks on the first channel verification target. All other user items (including login names) are not protected against enumeration attacks.

Enabling this flag has the following effects:

• The target item definition from the first channel verification step is protected from enumeration attacks.
• At any stage (except when persisting the user), conflicts with existing users are not reported for that item. Hence the channel verification step has to precede persisting steps.
• Any other unique user item (i.e. login names and items explicitly listed as 'unique' in Additional Unique Items), must not be valid according to the validation property configured for the first channel verification target. (E.g.: if channel verification is performed on the email address, no other unique item is allowed to be a valid email address).

false

Processors are notified at various stages of the flow and offer hooks for custom logic.

Custom Flow Processors Default Authentication Processors Default Authorization Processors Default One-Shot Authentication Processors Default Persistency-less Authentication Processors Default Persistency-less Protected Self-Service Processors Default Protected Self-Service Processors Default Public Self-Service Processors Default Technical Client Registration Processors Default Transaction Approval Processors Default User Self-Registration Processors