Hi all.
We want to integrate OpendistroKibana with WSO2 as Identity Server.
When accessing, it redirects us to the WSo2 page to enter the credentials. We enter them correctly and the IS responds to the callback URL with the corresponding code parameter. However, in Kibana it redirects to the login page instead of requesting the token and ending the flow.
We have done a test with Azure as Identity Server and the same thing happens to us.
We have configured the Kibana / openDistro part as it appears in the official configuration, but it does not work correctly.
These are the settings:
@igonzalez
I have the same problem and tried everything under the sun to no avail. I see that it redirects to the âŚ/auth/openid/login and never recovers from that.
Hi @pablo
Without proxy it doesnât work. The URL that is sent in the first step of the flow is not correct, so the subsequent redirection does not
The redirect URL in the Idp is: https: // myKibana / kibana / auth / openid / login
Hi @alphanero
Thatâs it. It always redirects to the IdP when it has already been authenticated and redirects with the corresponding code.
We have also tested with Azure as IdP and the result is the same
I donât know if there is someone for whom SSO based on the OIDC with Kibana / OpenDistro works âŚ
on checking the security audit logs - it looks like opensearch-dashboards is not receiving a username that it expects and hence redirecting back to IDP and then eventually fails.
I think that OpenDistro-Kibana receives a request of the type https: // myKibana / kibana / auth / openid / login? Code = XXX & state = YYY that it must process: retrieve the code to then make a POST to the / token of the IS with the corresponding parameters so that it returns the JSON with the âid_tokenâ that contains the user information.
But for some reason it doesnât identify the url as the answer from the IS and it redirects back to the auth page starting the loop again
Weird⌠For me I got the âtoo_many_redirectsâ error was because basic authenticator was the first one in the authentication chain, reply from keycloak doesnât contain properties awaited by basic authentication. To pass OIDC authentication first in the chain fixed this problem
FYI, I joined a copy of config.yml file for opensearch security and also opensearch-dashboard config file. This configuration works well for my authentication case with keycloak OIDC
Thank you, @vgiacomini
Unfortunately I have tried with the configuration you have sent and the same thing happens to me.
I now attach the configuration of our config.xml and the kibana.xml. Maybe something catches your attention and it is not correct.
Hello @pablo . We have started from scratch again and tested both HTTP and HTTPS.
The problem persists, however we see a warning in the Mozilla Firefox console: