-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Reinstate S3SearchableSnapshotsCredentialsReloadIT
in FIPS JVMs
#126109
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
Reinstate S3SearchableSnapshotsCredentialsReloadIT
in FIPS JVMs
#126109
Conversation
These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not.
Pinging @elastic/es-security (Team:Security) |
Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing) |
keystoreSettings.put("s3.client." + alternativeClient + ".secret_key", randomIdentifier()); | ||
keystoreSettings.put("s3.client." + alternativeClient + ".secret_key", randomSecretKey()); | ||
cluster.updateStoredSecureSettings(); | ||
assertOK(client().performRequest(new Request("POST", "/_nodes/reload_secure_settings"))); |
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.
The reload call needs to provide keystore password when in FIPS mode similar to this.
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.
Ah sorry for the noise I thought this had passed the FIPS tests when I asked for your review. Fixed that now.
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
💔 Backport failed
You can use sqren/backport to manually backport by running |
…astic#126109) These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not.
…astic#126109) These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not. Backport of elastic#126109 to `8.x`
These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not. Backport of elastic#126109 to `8.x`
Backport is #126324 |
…26324) * Reinstate `S3SearchableSnapshotsCredentialsReloadIT` in FIPS JVMs These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not. Backport of #126109 to `8.x` * CI poke
…astic#126109) These tests only don't work in a FIPS JVM because they use a secret key that is unacceptably short. This commit replaces the relevant uses of `randomIdentifier` with `randomSecretKey` so they work whether in FIPS mode or not.
These tests only don't work in a FIPS JVM because they use a secret key
that is unacceptably short. This commit replaces the relevant uses of
randomIdentifier
withrandomSecretKey
so they work whether in FIPSmode or not.