We are trying to implement authorization code grant type in Tyk Gateway. We have created a Oauth client through Gateway API.
When we try to call the Gateway API (/tyk/oauth/authorize-client/) to generate the auth code it is returning 404 error.
Do we need to call Gateway API for auth code or the actual API Definition which we have created with security policy? For token generation we are calling actual API Definition and its working fine.
Hey @Anup_Rai thanks for your question.
You can find more information on the tyk Oauth flows here: OAuth 2.0
There is also a video here: OAuth 2.0 that steps through the configuration of the Oauth 2.0 settings.
Under normal operation you would use the API endpoint url with /oauth/authorize-client/ appended. the gateway specific endpoint is for use cases where there may be restricted access to the dashboard API.
When I call API endpoint url with /oauth/authorize-client/ appended then call goes to upstream system.
For token generation it works fine, it generates the token and returns in response.
But for access code generation its not working as expected. We followed the documentation here.