-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Failing test: X-Pack OpenID Connect API Integration Tests.x-pack/test/oidc_api_integration/apis/authorization_code_flow/oidc_auth·js - apis OpenID Connect authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are provided #43736
Comments
Pinging @elastic/kibana-test-triage |
New failure: Jenkins Build |
Pinging @elastic/kibana-security |
It seems Elasticsearch can't get token from an endpoint that is exposed by our test Kibana plugin for some reason, I wasn't able to reproduce, but I'll keep trying. Just in case (since we still use ES from Aug 15th) - @jkakavas was there any ES OIDC issue that was fixed after Aug 15 and could have been the reason why ES couldn't retrieve token in exchange to authorization code? |
Nope... Is maybe something wrong with the dummy endpoint in Kibana (are there any logs that ES accessed that ) or could it be that ES is configured with the wrong URL for token endpoint ? |
Thanks for confirming. Yeah, likely something wrong with this test endpoint then, no logs there unfortunately. I'll see if I can reproduce.
Unlikely, it fails intermittently, just 3 times in a month. |
Well, now I'm wondering what this a)
b)
|
Ioannis recommended to try to increase ES HTTP client timeout settings and see if it helps:
I'm going to wait and see if this issue comes up again and then try to increase these timeouts, locally I couldn't reproduce it even with very low timeout settings.... |
Just had this fail in a PR |
Thanks for reporting, so I'll try to increase timeouts and see if it helps. |
I am getting the point a) issue. Is there any way to resolve that? Increasing the timeout value did not help.
|
Hi @soumendrak , please do not hijack threads. This github issue is specifically for the CI tests of Kibana. Please ask your user question in the forums, we have a very active community there and someone will hopefully assist you get your configuration in order. |
New failure: Jenkins Build |
Okay, it's been a month since last failure, closing for now. We'll see if it fails with the most recent ES versions when we switch to them. |
New failure: Jenkins Build |
Getting the same 401 somewhat randomly
|
I haven't succeeded in reproducing this issue this time as well... There is a chance it may be related to some of the token related issues we're going to fix soon, let's see. I'm closing this for now as we haven't seen any failed builds since March 6th. |
New failure: Jenkins Build |
Haha, that's a destiny 🙂 |
You couldn't have planned that any better 😆 |
29 days without failure, I'll give it one week more this time 🤞 |
🤞 |
Aha, good to know, thanks. Let me track that there then. I still hope it will be automagically fixed some day 🙂 |
Flaky test runner: https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/1407/ |
Flaky test runner passed with no failures, closing. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: