kong oauth2 route with GET method

[jeremyjpj0916]

Interesting, makes sense because Proxy is locked down to GET only but OFC if you enable oauth2 on it you would hope logic could over-ride that default to allow POST get the token specifically on that /oauth2/token path (but it does not apparently in your testing).

In the mean time here is a working alternative, setup a separate global token URL and enable global on the oauth2 token generation like I described here:

Enable OAuth2 for Multiple Services

Here is what I do for my gateway and I consider it to be a pretty good practice(I think documentation on Kong for best practices here would be helpful some time as the default behavior I consider to be a bit ehhhh). Step 1. Create an route of /auth with a service pointing to some dummy backend URL(it will never get called). Enable the Oauth2 plugin on this proxy with global_credentials set to true. You now have a clean endpoint like this to give to ALL clients for generating a Bearer token for …