Pinging @elastic/es-security (Team:Security)

I wonder why you didn't choose to enable it explicitly so the test runs on all builds?

Because in a release build the feature is supposed to be disabled, so it felt better to test the intended behaviour rather than force it to use a different behaviour.

The fact that we run this tests with the realm disabled actually uncovered the bug to be fixed in #84740 because this test failed when comparing the configured settings to the expected realm types, but it should have failed when configuring the realm (because the setting shouldn't exist).

@elasticsearchmachine run elasticsearch-ci/release-tests please

:qa:smoke-test-http:integTest

org.elasticsearch.client.ResponseException: method [PUT], host [http://[::1]:44137], URI [_cluster/settings], status line [HTTP/1.1 500 Internal Server Error] |  
{"error":{"root_cause":[{"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (reroute_after_cluster_update_settings) within 30s"}],"type":"exception","reason":"reroute after update settings failed","caused_by":{"type":"process_cluster_event_timeout_exception","reason":"failed to process cluster event (reroute_after_cluster_update_settings) within 30s"}},"status":500}

@elasticmachine update branch