Skip to content
This repository has been archived by the owner on Feb 10, 2021. It is now read-only.

Why LinkedAccount#providerUserId is called like this while its content is a hashed password? #323

Open
bravegag opened this issue Dec 21, 2016 · 0 comments
Open

Why LinkedAccount#providerUserId is called like this while its content is a hashed password? #323

bravegag opened this issue Dec 21, 2016 · 0 comments

Comments

@bravegag
Copy link
Contributor

Looking at the usage sample I am a bit puzzled on why the LinkedAccount#providerUserId is called like this while its content is a hashed password? Besides IMHO I don't think LinkedAccount requires a PK id it is superfluous as it is a Many-to-one user so it only needs the user_id as FK.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bravegag