Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 401 unauthorized error for openID #810

Closed
durgawaleajay opened this issue Aug 13, 2021 · 4 comments
Closed

[BUG] 401 unauthorized error for openID #810

durgawaleajay opened this issue Aug 13, 2021 · 4 comments
Labels

Comments

@durgawaleajay
Copy link

Describe the bug
401 unauthorized error for openID integration (Keycloak as IdP) for Kibana with openDistro security plugin

The authentication integration works fine for the 1st time. But once we restart the kibana we are getting the 401 unauthorized error. To make kibana work we need to delete the .kibana index every time we restart kibana.

We also observed that the security_authentication cookies is not getting created after the kibana restart which could be the cause of the 401 unauthorized error.

To Reproduce

  1. Integrate Kibana with openID security
  2. After starting Kibana kill the Kibana service
  3. Restart Kibana once again
    It will through 401 unauthorized

Plugins
opendistro_security

Additional context
Had raised a ticket in community below is the link & for work around as per comments we have downgraded the opendistro_security of elasticsearch from 1.13.1.0 to 1.13.0.0
https://discuss.opendistrocommunity.dev/t/kibana-401-unauthorized-error/6685/2

@vrozov
Copy link

vrozov commented Aug 13, 2021

@CEHENKLE CEHENKLE transferred this issue from opensearch-project/OpenSearch Aug 13, 2021
@CEHENKLE
Copy link
Member

Done

@Hariharan-Gandhi
Copy link

Hariharan-Gandhi commented Oct 11, 2021

I face the same issue too with OD_VERSION 1.13.2 ES_VERSION 7.10.2

@davidlago
Copy link

Apologies for the very late reply here. As multiple new versions (include major ones) have been released since, and this issue has not popped up, I'm going to go ahead and close this as potentially solved by one of them. If that is not the case, please reopen with more details. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants