Will Consider to add login_redirect_uri?

[devgodman]

I am going to build an web application to call Kong with kong-oidc to run authorization code grant flow and then access the upstream API. However, There is no login_redirect_uri. Ater running the authorization code grant flow, the request cannot redirect back to the browser but 400 bad request error is resulted.

Will you consider to add the setting login_redirect_uri to solve this problem. Thanks.

[cristichiru]

This final redirect (to the originally requested resource) is the callback URL you define in our OIDC client. It is automatic, as specified by the protocol, and for us it works just fine. There is no need for the parameter you request.

If you get 400 bad request, at least you should look at the logs at kong level and of course your app.

In our typical kong-oidc plugin config, we use something like: redirect_uri: /auth/redirect_uri. After authorization, the authz server is calling https://yourdomain.com/auth/redirect_uri, and then this one will redirect to whatever original page started the whole process.

In case something goes wrong, there is also recovery_page_path parameter of the kong-oidc plugin, where you can specify a fallback page, like the main page of your domain to fall back to, for example: recovery_page_path: /

Your API should be protected by the kong-oidc plugin, of course for all this to work, so when you try to access it, will trigger the flow.