OpenID connect fails with TOO MANY REDIRECTS

@Anthony : IT gets redirected to the URL which is added in AD and then fails to redirect back to Kibana app when tried the same configuration from HELM.

@Vikash The AD is returning localhost:5601… Therefore it’s looking for opensearch to be running locally, which is not the case probably with HELM. If the setup works locally with this test AzureAD, try to point docker-compose to your one and change the address to the FQDN or IP of your machine.

In my case, the cookie size was 6KB (6KB>4KB in browsers) and resulted in infinite redirects. This tutorial might help you Integrate Opensearch with Azure Active Directory

1 Like

@Vikash @tomas123 - How did you resolve the issue ?

@Malone It’s better to open a new thread and refer to the old one instead of bumping up an old thread.

Please create a new one and describe your scenario. Also, include your current version and config.yml file content.

@pablo Thanks. I ended up using SAML2 instead of OIDC for SSO and RBAC.