-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] Adjust assertions ReloadSecureSettings test for FIPS jvm #66965
[Test] Adjust assertions ReloadSecureSettings test for FIPS jvm #66965
Conversation
Pinging @elastic/es-security (Team:Security) |
equalTo("Provided keystore password was incorrect"), | ||
equalTo("Keystore has been corrupted or tampered with"))); | ||
assertThat(ObjectPath.eval("reload_exception.type", node), equalTo("security_exception")); | ||
if (inFipsJvm()) { |
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 "keystore is tampered with" is also thrown in fips, see #57050
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.
For this specific case, i.e. empty password, the error message should always be
Error generating an encryption key from the provided password
because it is generated without even reading the keystore file as opposed to other error messages. With this being said, I like @tvernum's suggestion as well. So we are settled here.
...rch/password_protected_keystore/ReloadSecureSettingsWithPasswordProtectedKeystoreRestIT.java
Outdated
Show resolved
Hide resolved
…csearch/password_protected_keystore/ReloadSecureSettingsWithPasswordProtectedKeystoreRestIT.java Co-authored-by: Tim Vernum <[email protected]>
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
@albertzaharovits @BigPandaToo I added more people as reviewers since I wasn't sure who would be around to help it out. But I really just need one approval for this simple change. Given @tvernum has approved it, I am going to merge it without further delay. Thanks! |
…tic#66965) When the JVM is configured to be in FIPS mode, the reload security settings API returns a different error message that is specific to FIPS when given an empty password. This PR adjust the assertions so that they are matched correspondingly. Co-authored-by: Tim Vernum <[email protected]>
…tic#66965) When the JVM is configured to be in FIPS mode, the reload security settings API returns a different error message that is specific to FIPS when given an empty password. This PR adjust the assertions so that they are matched correspondingly. Co-authored-by: Tim Vernum <[email protected]>
…) (#66966) When the JVM is configured to be in FIPS mode, the reload security settings API returns a different error message that is specific to FIPS when given an empty password. This PR adjust the assertions so that they are matched correspondingly. Co-authored-by: Tim Vernum <[email protected]>
…) (#66967) When the JVM is configured to be in FIPS mode, the reload security settings API returns a different error message that is specific to FIPS when given an empty password. This PR adjust the assertions so that they are matched correspondingly. Co-authored-by: Tim Vernum <[email protected]>
When the JVM is configured to be in FIPS mode, the reload security settings API returns a different error message that is specific to FIPS when given an empty password. This PR adjust the assertions so that they are matched correspondingly.
Resolves: #66880