The login journey encompasses a series of steps that guide customers through identifying their account, performing required authentication steps, and completing any missing account requirements needed to access an application.

Each of these steps contributes to the overall flow of validating the customer and ensuring secure access.

1. App launch: The login process begins when the brand's application starts a login flow with Strivacity.
2. Identify step: The first step involves identifying the customer through an identifier, such as username, email, phone, or external login credentials. This step can also determine the organization membership of the account.
3. Authenticate step: Once the identifier is provided, the system authenticates the customer based on the Adaptive Access policy.
4. Progressive profiling: This step captures additional customer information (for example, required attributes, mandatory consents) that are required before application access is allowed.
5. MFA enrollment: This step requires a user to register any outstanding MFA enrollment requirements, per the Adaptive Access policy.
6. OIDC token or SAML2 response generation: After successful authentication, the system generates an ID token, which can be an OIDC token or a SAML2 assertion, depending on the protocol in use.
7. Redirect: Finally, the customer is redirected to the appropriate destination after a successful login.

Each step in the login workflow can be affected by specific conditions, such as account lockouts due to failed password attempts or the presence of MFA requirements. Lifecycle event hooks can also be implemented at various points to trigger additional actions before or after key steps, for example, before password validation or after external login.

Extensibility points

Strivacity's customer journeys have various points where custom Journey Builder workflows and Lifecycle Event Hooks can be inserted to extend the natively configured workflows. These extensibility points are triggered by various events that happen during the customer journey.

There are two types of hooks: synchronous, which pauses Strivacity’s workflow until the script completes execution, and asynchronous, which runs the script without interrupting the workflow.

In the login journey, the following extensibility points are available: