3 ms·
> Your site did not create the redirect URI that is being passed to Google / Twitter in your example. Sorry, I don't understand this sentence. The redirect UR
by nailer 13y ago
> Your site did not create the redirect URI that is being passed to Google / Twitter in your example.
Sorry, I don't understand this sentence.
The redirect URI is not normally passed to Google / FB / Instagram dynamically, but normally registered with Google / FB / Instagram once, when you set up an app with them (and get a secret key etc).
If someone else registered their own app with their own redirector, they wouldn't have my secret key.
Edit: removed Twitter, they use oAuth 1 which is strange / different / weird.
- icebraining 13y agoNo, you do pass the URI dynamically, it's a required part of the Access Token Request: http://tools.ietf.org/html/draft-ietf-oauth-v2-16#section-4.1.3 http://tools.ietf.org/html/draft-ietf-oauth-v2-16#section-4.... It's just that with a decent implementation, you should also be required to register it beforehand with the provider.
- vertex-four 13y agoNot just a decent implementation; an implementation which meets the spec. This is not a problem with OAuth2, which explicitly requires registration of URIs where the implicit grant type is used, and covers other cases well in the Security Considerations section.
- nailer 13y agoThat makes a lot of sense: I've only really dealt with oAuth 2, as oAuth 1.0a is vastly more complicated and only Twitter seems to still use it. Thanks icebraining & vertex-four.