Thanks for the feedback, Niels,

I am primarily concerned about the email address, but as another attribute than the username is used to identify things, I thought I'd make sure and include that in the question too.

At some point, my customer will probably want non-unique email addresses. It's good to know it's at least on the roadmap.

Regards,

  Guus

On 12 April 2016 at 00:50, Niels Bertram <nielsbne@gmail.com> wrote:

Hi Guus,

I can't see how you could manage non-uniqueness of the username as you will need at least one user side unique identifier to drive forget password flow. But the option to have email non-unique has been discussed a while back in the user forum and there is this open Jira https://issues.jboss.org/browse/KEYCLOAK-2141.

We have been looking at non-unique emails and essentially one will have to remove the functionality of using email as a form of login from the login flow leaving the user to only be able to use their assigned or selected username as option. We have been trying to "hack" the codebase a bit but have not been too successful in getting keycloak to work properly with non-unique emails :( ...

Cheers,

Niels

On Tue, Apr 12, 2016 at 3:08 AM, Guus der Kinderen <guus.der.kinderen@gmail.com> wrote:

Hello,

Keycloak uses a UUID value to identify a uses. Basic questions: through some form of configuration:

• Can more than two users exist that have an identical username?
  
• Can more than two users exist that have an identical email address? 
  

Regards,

  Guus

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user