-
Notifications
You must be signed in to change notification settings - Fork 25.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
[Test] Fix failing ServiceAccountIT test #92953
[Test] Fix failing ServiceAccountIT test #92953
Conversation
by explicitly setting a host name to `localhost` instead of using default `_local_` address.
Pinging @elastic/es-security (Team:Security) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. lets wait if Mark has any comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine for now but I think as suggested in the original issue, the better option is to not enable FIPS on the test JVM for REST tests. As stated, it's all client code, not "code under test" so it doesn't make much sense to enable FIPS there.
@breskeby @mark-vieira Thank you both for the review. |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
This commit adds a workaround for failing `ServiceAccountIT` test by explicitly setting a host name to `localhost` instead of using default `_local_` address. Relates to elastic#92930 (cherry picked from commit 96d3fce)
This commit adds a workaround for failing
ServiceAccountIT
testby explicitly setting a host name to
localhost
instead of using default_local_
address.Relates to #92930