Imported Google Group message.
Date:Thursday, 2 April 2015 15:46:15 UTC+1.
Tyk can act as an OAuth server, in this case your applications sounds like an OAuth client, which would mean your application and the authenticating OAuth provider need to speak to one another directly.
If you are integrating authentication with a third paty OAuth provider, then essentially you are validating a users identity, you would usually, once the validation has taken place and the third-party authoriser has granted you a toekn to access the data providers user data, you would store that token alongside a local user record (so you can use it in future logins and populate your user record with their data), how this user then accesses your API is up to you - you could generate a key for them (with the Tyk REST API), store the returned key alongside the same user record and issue it to the user, they can then use this key to access your API (since signup is now completed) via Tyk.
I may be off the mark here - OAuth is pretty broad, what exactly are you trying to achieve?
On Thursday, April 2, 2015 at 3:32:12 PM UTC+1, Mathijs Van den Worm wrote:
I'd like to use a third-party as an Oauth provider (e.g Facebook, Google or GitHub) but I can't seem to get it to work. Is it possible and if so could you tell me how?