User Journeys

A user journey is the sequence of steps a user goes through to reach a goal with cidaas: signing in, registering, regaining access to an account. With user journeys you design these flows yourself. You start from the cidaas standard flow and add your own steps: pages that the user sees and calls to your own systems.

For: identity architects, product owners and developers who want to align sign-in, registration and recovery with their business processes.

Typical use cases:

• Check during registration whether the person is already in your CRM and link the customer number.
• Register a business user together with their organisation and add them to a user group.
• Ask for an additional consent before the token is issued.
• Check your master data before a user may recover an account.

Available user journeys

LoginloginSign in to an application.OnboardingregisterCreate an account: self registration, invitation, B2B.Account recoveryaccount_recoveryRegain access when the usual sign-in no longer works.

Account verificationaccount_verificationVerify an email address or mobile number.

SigningsigningConfirm a transaction or document.

More user journeys will follow.

How a user journey works

A user journey is a chain of tasks. cidaas runs one task after the other:

• Interactive tasks show a hosted page and wait for the user, for example the login form.
• Automated tasks run on the server without a page, for example a call to your API.

Each task can have a pre condition: if it is not met, the task is skipped. A post condition can send the user back to an earlier interactive task, for example to correct an entry. Tasks share data through the journey context. See Journey model.

What you can customize

You do not write a user journey from scratch. You copy the standard flow of a journey and add your own tasks at defined places, the injection points:

1. Add interactive tasks: show your own hosted page, for example to collect company data.
2. Add automated tasks: call your own API through cidaas, for example to check a customer number.
3. Control the flow: decide with conditions when your tasks run, and pass data between tasks.

Security steps such as multi-factor authentication, uniqueness checks and token issuance remain with cidaas. Your tasks can add requirements; they cannot remove or weaken the steps cidaas requires. See Custom tasks.

What else determines the flow

The tasks that actually run for a user depend not only on the journey definition but also on your configuration and on the user:

Source	Example
Verification options of the application	Which authentication methods are allowed, when MFA is required
User setup (registration fields)	Which fields are requested and which are mandatory
Authorization settings of the application	Requested scopes, consents, group selection
The user's own settings	Which verification methods the user has enrolled, which identifier (email, mobile number) the user uses

Different journeys per application and channel

Which flow is used for a journey is set in the hosted pages layout: for each journey ID you bind one flow. The layout is assigned to an application in the app configuration. You can therefore use different journeys per channel, for example a short login for the mobile app and a login with an additional consent step for the partner portal.

Compatible hosted pages

The hosted pages you know today keep working. If no own flow is bound for a journey in the hosted pages layout, cidaas uses its standard flow with the compatible hosted pages. You can switch journey by journey and application by application.

The compatible hosted pages and their configuration are described here:

Page	Used in
Login page	Login
Registration page	Onboarding
Initiate verification page	Login (verification, MFA)
Suggest verification page	Login (set up additional methods)
Consent page	Login
Group selection on login	Login
Account deduplication	Onboarding
Password pages (forgot, reset, change)	Account recovery, login
Device success page	Login with the device code flow

Theme, layout and translations apply to compatible and custom pages alike: see Hosted Pages Management, Theming and Translation.

Next steps

Journey modelTasks, conditions and the journey context.Custom tasksInjection points, custom hosted pages and your own APIs.Compatible hosted pagesTheme, layout and translations of hosted pages.

Need Support?

Please contact us directly on our support page or reach out to cidaas support at [email protected].