-
Notifications
You must be signed in to change notification settings - Fork 555
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.
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
Repeat password on sign up #61
Comments
We should make this optional, but as you say, a good default Martin Gontovnikas Twitter: @mgonto (https://twitter.com/mgonto) On Thursday, 16 de October de 2014 at 08:47, José F. Romaniello wrote:
|
Social only layout height is zero
Moved to internal backlog |
@hzalaz Was this ever implemented? Can't see it anywhere in the docs |
We would very much like to use this feature, if it has been implemented. |
Any news on this? Don't see anything in the docs. |
No news. This is not supported, that's why there's no docs about this. |
That's so strange, seems like a pretty basic thing... |
+1 |
+1 |
+1 |
+1 |
1 similar comment
+1 |
+1, please! |
Could you please give a statement why you are not implementing such a basic feature. In my opinion is is pretty easy to implement and a must have for an authentication platform. I only want to understand the reasons behind it. |
We're focusing on other areas right now and there's no plans to implement this into Lock as of now. |
This is critical feature and makes sign up process very dangerous! How can you possibly not implement it for 4+ years despite of your clients begging for it ? |
Hi, I could not find any information about contributing to this project, but maybe someone from community could propose PR with this feature? Is there a chance it would be merged and released? |
+1, we could really use this feature as well. |
+1 |
I hate being that person, but I want to also drop a request for this to be implemented. I don't know of many other sign up forms that don't ask for a password confirmation. Many times a week users sign up with their password as their name, since that's the field that's right after the password input. This obviously causes issues where users are not happy about their password being exposed like that. Users usually assume we're saving their auth info in plain text because of this. If there's any suggestion for fixing that (which doesn't require this feature to be implemented) I'm all ears. If not, I give a healthy +1 for the internal tracking ticket you all have 💯 |
+1 |
1 similar comment
+1 |
Have to agree with everyone else here: this is a very basic feature and it is rather surprising that Lock does not support this. Please reconsider! |
+1 |
Still not added this feature? 6 years later? Wow !! |
+1 |
Without a "confirm password" field, it looks like a login page. It's confusing for some people. |
Still +1 |
+ 1, This thread is very disappointing. Anywhere else to make feature requests that also get implemented? |
I would encourage you (and everyone else in this thread) to register their interest at Auth0 Feedback. |
Good idea! Done. Note to all: Let's do this but remember the maxim "you catch more flies with honey than vinegar" in our feedback. As I am not a pest control specialist nor an entomologist I can't vouch for the literal truth of that but you get the point! Come to think of it, don't you catch fruit flies with cider vinegar? Oh well... |
Are there any plans to implement this? I am extremely confused and disappointed why it isn't supported yet, considering the issue was opened seven years ago. Adding a simple password confirmation field is trivial and supported by pretty much any app out there... |
We are using the paid version and we really need it. |
+1 . How is this still not there? |
+1. |
+1. |
+1 |
2 similar comments
+1 |
+1 |
+1 in 2023... |
Again I would encourage you to register their interest at Auth0 Feedback. This feature is actually owned by a different team other than us simply maintaining this SDK, and so the best place to register this interest would be that product feedback page. |
Currently we ask for the password twice on reset but only once on sign up.
I think this is a good default but we should have an option to ask twice for the password on sign up.
This will depends on the target audience for the application.
The text was updated successfully, but these errors were encountered: