Configure user self-service journeys
You must configure user self-service journeys in PingOne Advanced Identity Cloud before your end users can experience them. For example, you can configure journeys for password reset, username retrieval, and more.
Use cases for user self-service
You must configure Advanced Identity Cloud to let end users service their own accounts.
For example, if you want to let end users register themselves with Advanced Identity Cloud in order to create their own identity, you must create a journey that collects required information. Then you must test the journey and push the journey’s configuration to your production tenant.
The features end users' can access depend on the configurations you make.
The following is a table referencing various actions you can take as an end user in Advanced Identity Cloud (if you configure them). Some links refer to information from Ping Identity Knowledge Base and the Ping Identity Community.
You can configure these self-service journeys:
| Use Case | Description |
|---|---|
Simple login journey collecting username and password. |
|
Journey for end users to recover their username. |
|
Allow end users to reset their password using a journey. |
|
Allow end users to update their password, after being logged in with a session. |
|
Allow end users to register their own identity in Advanced Identity Cloud. |
|
Allow end users to use social providers, such as Google or FaceBook to login. |
|
Ask users for more information based on login count. |
|
Validates an end user’s password with a remote system. Use when Advanced Identity Cloud password synchronization doesn’t support the remote system’s hash algorithm. |
|
Create a journey to allow end users to log in with a recovery code if they lose their device. |
For further use cases and questions about configuring the Advanced Identity Cloud end-user UI, learn more in FAQ: Identity Cloud hosted End User UI.