Replies: 4 comments 1 reply
-
No, nothing should depend on the username having specific content. FWIW, we might also reconsider our separation of usernames and emails; I've fought against this before but I'll concede that I find that approach useful. |
Beta Was this translation helpful? Give feedback.
-
(See essentially the same proposals at #4053) |
Beta Was this translation helpful? Give feedback.
-
Hello, I wanted to ask if there was any work done with regards to this issue. From what I checked this is not solved, but the original issue 906 was defined as closed. We started using OJS and our first user had problems registering because of this error. He thought there was an issue with his password... I would like to know is if there is a way to change up the error message because it seems to be confusing to users. |
Beta Was this translation helpful? Give feedback.
-
We started testing the OMP with a Brazilian publisher indexed in SciELO and that was the first question. This implementation would be very useful. |
Beta Was this translation helpful? Give feedback.
-
What is driving the requirement that "The username must contain only lowercase letters, numbers, and hyphens/underscores."?
With Shibboleth authentication, the best practice username would be a scoped attribute, eg. user@institution-scope (usually this is just an email address).
Are there any known dependencies that will break if we loosen the username validation?
Beta Was this translation helpful? Give feedback.
All reactions