-
Notifications
You must be signed in to change notification settings - Fork 148
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
After Login Success API Calls using access token from Oauth2 providers #61
Comments
Hi @afdecastro879 There is currently no solution for that and I will not have the time to implement it soon. So I would very welcome a PR on it :) I think it is rather simple to do a post login callback, but there are multiple possible ways to do this:
I would provide to the callback a rather big set of information:
The callback could be called in this line: The callback also could return
Further: To be consistent, it would be good to provide the callback functionality also for the non OAuth Login Backends. For them, the callback could also be called here: It would be very cool, if you get your hands on this! See the above just as an idea .. there may also be smarter solutions .. |
@smancke I just have the time again to look at this issue. I have some questions
go callbackFunction()
return false, true, userInfo, err So the callback does not become blocking if the callback operation takes too much time. What do you think? Let me know so I can clarify the ideas around the issue and start getting my hands on this Cheers |
I've been struggling a little bit finding a way to use the access token for after-login-success API calls to Github and Bitbucket providers. Is there a way I can use the access token, send it somewhere in my code to be saved?
I've seen #8 seems to be the solution to this problem using a post login call back. Will this issue be solved on the short term? Does someone know a way I can actually do a workaround in the meantime? I'm also open to eventually do a contribution but I don't know where or how to start. Any ideas?
Thanks a lot
The text was updated successfully, but these errors were encountered: