Make OTP Input Page Similar to Post-Login OTP Page

[r0x5r]

Preliminary Checks

• I have reviewed the documentation: https://unkey.com/docs

• I have searched for existing issues: https://github.com/unkeyed/unkey/issues

• This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.

Reproduction / Replay Link (Optional)

No response

Issue Summary

Please change the OTP verification page to match the design and functionality of the page that appears after logging in and asks for an OTP. Currently, the OTP page allows more than 6 characters, whereas it should only accept 6 digits. The post-login OTP page has a better design, where only 6 digits can be entered, and no errors are shown for valid input.

Steps to Reproduce

1:- go to this page https://app.unkey.com/settings/user
2:- add other user mail
3:- click on verify
4:- enter false otp

Expected behavior

he OTP input page should be redesigned to work exactly like the post-login OTP page, where the input is restricted to 6 digits and the field prevents any extra characters.

Other information

Actual Behavior:

The current OTP page allows more than 6 characters and displays an error after submission.

Suggested Fix:

Update this OTP input page to match the design and functionality of the post-login OTP page.

Screenshots

Version info

- url:https://app.unkey.com/settings/user
- Node:
- npm:

[linear]

ENG-1526 Make OTP Input Page Similar to Post-Login OTP Page

[igabhix001]

/assign

[oss-gg]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest

[igabhix001]

Hi! I'd like to work on this issue. Could you please assign it to me? Thanks!

[perkinsjr]

We won't be fixing this, as we are transitioning to our new auth provider shortly.

cc @mcstepp

[perkinsjr]

/award 50

[oss-gg]

Awarding r0x5r: 50 points 🕹️ Well done! Check out your new contribution on oss.gg/r0x5r

[GARY121github]

@perkinsjr can I work on this issue since it has not been solved yet?

[chronark]

@GARY121github see

We won't be fixing this, as we are transitioning to our new auth provider shortly.

cc @mcstepp