-
-
Notifications
You must be signed in to change notification settings - Fork 52
Support for multiple apps/project (duplicate users) #114
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
Comments
This is up to your implementation, this package is not scoped for user management. In my projects we have an authenticated / authorized route (authorization code grant workflow) that returns the user's identity and there we fetch user by id. Maybe you add some code snipped on how you currently retrieve your user and maybe we can make a generic solution as example for the documentation out of it. |
All I got for fetching the user is username and password, assuming username usually is email, it won't allow multiple apps/project for same users So I want to fetch user by I think it will be sufficient if you add client argument to password grant. return Promise.bind(this)
.then(function() {
return this.getUser(request, client);
})
.then(function(user) {
return this.saveToken(user, client, scope);
}); and then This is just my idea, not sure if that solution is against some rules of OAuth2 ? |
I think this would be a good improvement to provide the client in the getUser (username: string, password: string, client?: Client) {
} |
@jorenvandeweyer I agree but let's add this to release 5.0.0 |
Implemented by #256 @jankapunkt Do you think you can create a new RC? |
Of course, coming in today |
I was just creating my own OAuth2 server base on this repo.
Main advantage in my head was, that I can use this server for multiple projects, but with that it means usernames could be duplicates, e.g. same users for different apps.
my idea was, to store users, against
clientId
however ongetUser
we don't haveclientId
to fetch it by.Is there something I am missing ? is there better way to do it currently?
Or is it even a good idea to do it at all ?
The text was updated successfully, but these errors were encountered: