You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a backend service which is proxied using kong. We need to enabled OIDC authentication for this service and we are using this oidc plugin. Okta is our Identity Provider. We have the following configuration in our .yaml file for the service/route at kong along with oidc plugin configuration
When we access the route through kong i.e , kong successfully redirects to Okta for authentication. After providing authentication credentials, Okta successfully redirects the request back https://app1.host1/somepath with authorization code and state parameter in the URL. However, kong throws the following error
request to the redirect_uri path but there's no session state found
Please note that the similar configuration is working fine in another environment (another instance of kong with another instance of Okta). So we are unsure what would be causing this issue. Any ideas or pointers regarding it would be highly appreciated.
The text was updated successfully, but these errors were encountered:
Hi,
We have a backend service which is proxied using kong. We need to enabled OIDC authentication for this service and we are using this oidc plugin. Okta is our Identity Provider. We have the following configuration in our .yaml file for the service/route at kong along with oidc plugin configuration
When we access the route through kong i.e , kong successfully redirects to Okta for authentication. After providing authentication credentials, Okta successfully redirects the request back https://app1.host1/somepath with authorization code and state parameter in the URL. However, kong throws the following error
request to the redirect_uri path but there's no session state found
Please note that the similar configuration is working fine in another environment (another instance of kong with another instance of Okta). So we are unsure what would be causing this issue. Any ideas or pointers regarding it would be highly appreciated.
The text was updated successfully, but these errors were encountered: