FTR should use the new kibana_system user (#120436) (#120626)

* FTR should use the new kibana_system user

* Fix security api integration tests

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Rudolf Meijering <rudolf.meijering@elastic.co>
This commit is contained in:
Kibana Machine 2021-12-07 10:59:27 -05:00 committed by GitHub
parent 15bb1dc787
commit 2aaca4681c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View file

@ -14,7 +14,7 @@ export const kibanaTestUser = {
};
export const kibanaServerTestUser = {
username: env.TEST_KIBANA_SERVER_USER || 'kibana',
username: env.TEST_KIBANA_SERVER_USER || 'kibana_system',
password: env.TEST_KIBANA_SERVER_PASS || 'changeme',
};

View file

@ -150,7 +150,7 @@ export default function ({ getService }: FtrProviderContext) {
enabled: true,
metadata: {
pki_delegated_by_realm: 'reserved',
pki_delegated_by_user: 'kibana',
pki_delegated_by_user: 'kibana_system',
pki_dn: 'CN=first_client',
},
authentication_realm: { name: 'pki1', type: 'pki' },
@ -187,7 +187,7 @@ export default function ({ getService }: FtrProviderContext) {
enabled: true,
metadata: {
pki_delegated_by_realm: 'reserved',
pki_delegated_by_user: 'kibana',
pki_delegated_by_user: 'kibana_system',
pki_dn: 'CN=second_client',
},
authentication_realm: { name: 'pki1', type: 'pki' },