Feature: Add a second input to confirm the password on signup when using the new universal login
Use-case: When using the new universal login, the sign-up page looks like a login page because there is no password confirmation. I think the second password-input is something many users expect to find on the sign-up page. In combination with organization-invitations we already observed customers searching for a given password in the invitation-mail. So the lack leeds to a lot of confusion.
I would suggest to make this an optional setting, so that tenant administrators can decide whether to have password confirmation or not.
I found a lot of posts in the help-section asking for that feature:
@SaqibHussain following up with you from your thread here, any resolution / ETA on password confirmation field? This has been reported by many of our users and is quite important to us
Hi @SaqibHussain I have submitted feedback but have not heard back yet. This is still a strong bottleneck for our users. Would you please be able to share more from a timeline perspective?
I’ve checked the item on our end (Password confirmation with New Universal Login) and there are no timelines for delivery of this one, it still looks early days, however I have added a comment with a link back to here for reference so when it is reviewed the comments here will be visible.
confirm password field for signup page in new universal login should have been implemented by default. There are too many cases where this confuses users and they think it is a login field. This should be a high priority for the product team.
@SaqibHussain Any updates internally about this feature request? Specifically in relation to the New Universal Login widget for Organization Invitations
We also need this feature to help differentiate login from signup (a signup would not be mistaken for a login if it had a password confirmation input).
Our organization is currently blocked from leveraging Auth0 to facilitate signups due to the absence of this. Could you provide any updates on the timeline or progress for implementing this feature?