Closed kanes115 closed 3 years ago
Yeah, that makes sense.
Currently Assent OAuth 2.0 strategy only supports authorization code grant flow. I'm not sure if this is implicit grant flow, but I'll dig into the facebook docs to see how I should deal with the callback phase.
So it looks like this would be specific to facebook instead of implicit grant flow:
As I understand it, this decodes the short lived access token from a cookie using the client secret, and then uses it to generate a long lived access token. Not sure if necessary with Assent, but I guess it can't hurt.
Edit: Facebook also suggests using code grant flow https://developers.facebook.com/docs/facebook-login/security#codeflow. I'll have to test this manually to see how it all works.
Also, this lib is probably the best reference: https://github.com/facebook/php-graph-sdk/blob/6d1eb5a3861624cd0ff40c67e517de891d78134a/docs/reference/FacebookJavaScriptHelper.md
I've set up instructions for how to deal with Facebook JS SDK here: https://github.com/pow-auth/assent/pull/44
I'll close this as I believe both #44 and changes in the OAuth 2.0 strategy has made it very easy to handle with already fetched access token in client.
To recap:
code
client side to submit server sideAssent.Strategy.OAuth2.get_access_token/3
to fetch the access token. Callback still uses the authorization code flow.Assent.Strategy.Facebook.get_user/2
could be used to fetch the user data with the access token.
Right now assent assumes that the client will pass
code
in parameter list in the callback phase. There are cases, though, when the client has an access token already (assent does not need to fetch it and does not have the means to do so). Would it be possible and desirable to accept access tokens as well in OAuth2 strategy.My specific use case is Facebook login on mobile devices where client side libraries only allow to fetch the access token straight away.