Registration sign up page to allow entering the code sent via email

[Comoque1]

Description

As a User I want to have minimal pages, through which I have to go, to finalize registration flow

• When user is on ./registration page and press SIGN UP button, he is redirected to ./registration/success
• The page ./registration/success has 1 link (to trigger verification flow again) and "Continue" button to navigate to Home page
• At the same time an email containing code and verification link with code are sent to the user
• If the user wants to use the code, there is no place to fill it up on ./registration/success. The result of this is - user must click on the link to redirect him to verification page and to retrigger the flow or to open the link received in the email

Acceptance criteria

• [ ] On ./registration/success page add the verification flow input field and buttons

Note: the text to say thank you with instructions also needs to be added / updated.

Additional Context

Link to Figma: https://www.figma.com/file/zgJpVXeEeKNitXM8Nv5STK/Registration-sign-up-page?type=design&node-id=1%3A50&mode=design&t=JBX44HKu7RmpjDyX-1

[valentinyanakiev]

@SimoneZaza @techsmyth I think this will be technically feasible, but it doesn't make a lot of sense from UX perspective to me.

What we have at the moment:

1. User registers
2. He is redirected to a page that says the user has received an email, and the user needs to check the email and click on a link.
3. After clicking the link, the verification page is opened with the code already inserted.
4. The user clicks on the button and verification is complete.

What I perceive you are proposing:

1. User registers
2. He is redirected to a page that says the user has received an email, and the user needs to check the email. The email has a link and a code (that's what Kratos provides) and the user needs to copy the code from the email.
3. User goes back to the previous page and pastes the code.
4. The user clicks on the button and verification is complete.

Quite frankly, I am a user, and I'd rather just click a link and have it auto-filled + page auto-routed to me. If we alter the process, we will end up with 2 flows, because some users will click on the link, some won't, or we need to alter the template and force them to copy-paste, which, again, can be error prone. I sincerely believe this will create more problems than solutions.

[valentinyanakiev]

Just to make this 100% clear, there is no way to avoid the user checking the mail, this is the key security step in the verification.

[SimoneZaza]

A short summary of what we've discussed together in a call:

• Indeed, for many users a clickable link in the email provides the best experience, this link should stay
• However, showing an input field for a verification code is a very clear prompt to go and check your email. Also, some users avoid clicking links from emails for security reasons
• The users can then decide themselves what way of verifying they prefer: clicking on the link, copy/pasting the code, or trying to remember it and using the verification process as a quick brain workout 😉

[techsmyth]

The registration flow ID is not available, so this story is not feasible in the above description,