mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-15 01:16:09 +00:00
74dbdb991c
If security was disabled (explicitly), then the SecurityContext would be null, but the set_security_user processor was still registered. Attempting to define a pipeline that used that processor would fail with an (intentional) NPE. This behaviour, introduced in #52032, is a regression from previous releases where the pipeline was allowed, but was no usable. This change restores the previous behaviour (with a new warning). Backport of: #52691
30 lines
1.2 KiB
Groovy
30 lines
1.2 KiB
Groovy
/*
|
|
* This QA project tests the security plugin when security is explicitlt disabled.
|
|
* It is intended to cover security functionality which is supposed to
|
|
* function in a specific way even if security is disabled on the cluster
|
|
* For example: If a cluster has a pipeline with the set_security_user processor
|
|
* defined, it should be not fail
|
|
*/
|
|
|
|
apply plugin: 'elasticsearch.testclusters'
|
|
apply plugin: 'elasticsearch.standalone-rest-test'
|
|
apply plugin: 'elasticsearch.rest-test'
|
|
|
|
dependencies {
|
|
testCompile project(path: xpackModule('core'), configuration: 'default')
|
|
testCompile project(path: xpackModule('security'), configuration: 'testArtifacts')
|
|
testCompile project(path: xpackModule('core'), configuration: 'testArtifacts')
|
|
}
|
|
|
|
testClusters.integTest {
|
|
testDistribution = 'DEFAULT'
|
|
numberOfNodes = 2
|
|
|
|
setting 'xpack.ilm.enabled', 'false'
|
|
setting 'xpack.ml.enabled', 'false'
|
|
// We run with a trial license, but explicitly disable security.
|
|
// This means the security plugin is loaded and all feature are permitted, but they are not enabled
|
|
setting 'xpack.license.self_generated.type', 'trial'
|
|
setting 'xpack.security.enabled', 'false'
|
|
}
|