You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Backport 7.11] Add a smoke test for security realms (#68951)
This changes adds a new QA test that runs a smoke test on a node that
has been configured with one realm of each type.
Not all of the realms work, because some of them would depend on
external fixtures (LDAP, SAML, etc) and this particularly test suite
is intended to be as stable as possible and have no external
dependencies.
The primary purpose of this test is to catch any issues that prevent
a node from starting with particular realms configurd (e.g. security
manager or classpath issues). We don't depend on external fixtures
becaused we want this to be a smoke test that clearly indicates when a
(seemingly unrelated) change in Elasticsearch has unintended
consequences on realms. The use of external dependencies would
increase the number of things that could go wrong and move this from a
smoke test to a potentially noisy integration test.
Backport of: #68881
* This QA test is intended to smoke test all security realms with minimal dependencies.
3
+
* That is, it makes sure a node that has every realm configured can start, and tests those realms that can be tested without needing external services.
4
+
* This tradeoff is intentional because we want this set of tests to be very stable - failures in this QA suite should be an indicator that
5
+
* something is broken in Elasticsearch (and not that an external docker fixture broke)
6
+
* This test is also intended to work correctly on FIPS mode because we also want to know if a realm breaks on FIPS.
0 commit comments