Open shane-rice-bfg opened 7 years ago
I have noticed this as well. I'd love a PR for it if you can, otherwise I'll take a crack at it.
@shane-rice-bfg have you had a chance to look into this?
No, I have not. We have moved away from OAuth for this application.
was this fixed? what is the solution to contribute?
Hello @jleclanche
Id like to give this a go Any pointers/suggestions on how to approach this issue?
Hello @jleclanche
Id like to give this a go Any pointers/suggestions on how to approach this issue?
@bull500 This is a really old bug report, so please make sure it still actually exists and feel free to submit a PR!
@bull500 This is a really old bug report, so please make sure it still actually exists and feel free to submit a PR!
hello @n2ygk
I did the Auth Code flow twice to test this. The access tokens are different for me
On the http://127.0.0.1:8000/o/authorized_tokens/ page i do see the same app twice with individual token revoke links
I am using the framework, and it seems to work flawlessly, except every time the user logs in a second time, it duplicates the authorization in at the
o/authorized_tokens
endpoint.Is there any way to prevent duplicate authorizations, or automatically remove the previous authorization upon a second login?
Currently the user can log in to all applications with out a password after the first authorization and as long as their logged into this oauth server, but each login create the duplicate client application, which is unsightly and hard to mange authorizations for the clients.