Moved Ruby ValidatedPassword setting to Java implementation

[andsel]

Release notes

[rn:skip]

What does this PR do?

Translates ValidatedPassword setting class into plain Java. This PR copies the Rspec test also to JUnit, plus removed a log validation test, because mocking of the ValidatedPasswordSetting Java class seems to do not work in Rspec.

Why is it important/What is the impact to the user?

N/A

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• [ ]

How to test this PR locally

On config/logstash.yml enable basic authetication on HTTP API with an invalid password and configure password_policy.mode to warn a log message:

api.auth.type: basic
api.auth.basic.username: "logstash-user"
api.auth.basic.password: "invalid"
api.auth.basic.password_policy.mode: WARN 

run Logstash:

bin/logstash -e "input{stdin{}} output{stdout{codec=>rubydebug}}"

and verify that in log appears:

[WARN ][org.logstash.settings.ValidatedPasswordSetting] Password must contain at least one upper case, must contain at least one digit between 0 and 9.

and doesn't crash.

Related issues

• Closes Reimplement LogStash::Setting::ValidatedPassword to Java #18184

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label. Could you fix it @andsel? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• If no backport is necessary, please add the backport-skip label

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 37653a5

Failed CI Steps

• :java: Java unit tests - FIPS mode

History

• 💛 Build #3530 was flaky fc2e9aa
• 💛 Build #3522 was flaky 6ca07fb

cc @andsel