Skip to content

fix: unified reg #2118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
+10 −24
Draft

fix: unified reg #2118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file removed docs/identities/sign-in/_static/two-step-registration.png
View file
Open in desktop
Binary file not shown.
34 changes: 10 additions & 24 deletions docs/identities/sign-in/two-step-registration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,30 +5,16 @@ sidebar_label: Two-step registration
slug: two-step-registration
---

With a one-step registration, when you enable multiple authentication strategies (for example password, code via email, and
passkey), the identity traits will be repeated for each authentication strategy.
[Identity traits](../../kratos/manage-identities/managing-users-identities-metadata#traits) are data associated with an identity
that can be modified by the user. The traits are configured through the identity schema.

Compare this to a two-step registration: Now, the user is prompted for the identity traits in the first step, and asked to choose
a credential method for authentication next. This results in a more stream-lined user experience.
With a one-step registration - also called _unified registration_ - the identity traits will be repeated for each authentication
strategy. For example the identity traits will be repeated for the password, the code via email, and the passkey method. For this
reason unified registration is recommended for use cases where you have only one or two authentication methods enabled.

:::info
With a two-step registration - also called _profile-first registration_ - the user is prompted for the identity traits in the
first step, and asked to choose a credential method for authentication next. This results in a more stream-lined user experience
when you have more than two authentication methods enabled.

Identity traits are data associated with an identity that can be modified by the user. The traits are configured through the
identity schema.

[Learn more about identity traits](../../kratos/manage-identities/managing-users-identities-metadata#traits)

:::

![Registration with two-step registration vs one-step registration](./_static/two-step-registration.png)

To disable the legacy one-step registration, Go to <ConsoleLink route="project.authentication" /> and switch off **Enable legacy
one-step registration** or use the Ory CLI:

```bash
ory list workspaces # to get the workspace id
ory list projects --workspace <workspace-id> # to get the project id

ory patch project --project <project-id> --workspace <workspace-id> \
--replace '/services/identity/config/selfservice/flows/registration/enable_legacy_one_step=false'
```
To disable the one-step unified registration, Go to <ConsoleLink route="project.settings.advanced.route" /> and disable **Enable
unified sign up**.
Loading