Skip to content
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

Duplicate users #19

Open
maksym-prikhodko opened this issue Oct 24, 2019 · 1 comment
Open

Duplicate users #19

maksym-prikhodko opened this issue Oct 24, 2019 · 1 comment

Comments

@maksym-prikhodko
Copy link

The first user(ID 1) has been signed up via generic login
The second user (ID 6) has been signed up via Google Provider, it looks like duplicated users. Have You any ideas or maybe You know any way to find the solution?
screen

@cubiclesoft
Copy link
Owner

They are unique accounts from the perspective of the SSO server. Account ID is the only unique attribute you can ever truly rely upon and trust from a client application perspective. Per-provider, the account is unique. Email address is actually an unreliable mix-down metric. For example, Google doesn't always supply an email address for every user (e.g. very old, pre-GMail accounts), Generic Login can be set up as Username only, and ActiveDirectory could supply 150 email aliases for a user. The goal is generally to normalize all of that information as best as possible. However, it can result in confusing end-user experiences - especially for users with accounts on multiple providers - Which one did I sign in with again?

That said, I do have on my internal project list to add a new database field to provide a shared ID mapping option, which would allow selection of a shared ID field (e.g. email address). This comes with all kinds of caveats. For example, the Remote Login provider would have to be carefully excluded because that provider could be used to push anything into the system, allowing any authorized Remote Login system to sign in as any user in the SSO server. That would definitely not be good. However, as the SSO server is designed currently, what I described is impossible with Remote Login since each provider is isolated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants