[Security Solution] Update serverless FTR tests to not run with operator privileges

[machadoum]

Summary

• Create a new service that replaced the serverless supertest with a custom implementation that adds auth headers
• username updates
  • Update SessionManager to store username
  • Create and export securitySolutionUtils to return the username
  • Update tests to use the getUsername helper
• Create a helper that allows switching serverless roles on a test

export default ({ getService }: FtrProviderContext) => {
   const utils = getService('securitySolutionUtils');

   describe('@ess @serverless my_test', () => {
      let supertest: TestAgent;

      before(async () => {
         supertest = await utils.createSuperTest('admin');
      });
   ...

• Update FTR tests README file with further details

Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/6320

Know issues

• Currently utils.createSuperTest('viewer') fails on the API creation. It will be fixed by @elastic/kibana-security [POC] Serverless API integration test helper - create API key as admin #184948

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed

[machadoum]

/ci

[machadoum]

/ci

[machadoum]

/ci

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[machadoum]

/ci

[wayneseymour]

Just one question so far.

[wayneseymour]

Sorry about the false LGTM, but I do have one question.

[MadameSheema]

One question: What's the expectation for updating the tests for less-privileged roles once the #184948 is resolved? Will your team update all the affected tests or should every test-owning team do it?

@nikitaindik each team should take care of their tests for that specific case :)

[machadoum]

One question: What's the expectation for updating the tests for less-privileged roles once the #184948 is resolved? Will your team update all the affected tests or should every test-owning team do it?

@nikitaindik
The expectation is that every team updates its tests mainly because the team that owns the tests knows which role is more appropriate for it. The change should be minimal. Like:

- supertest = await utils.createSuperTest();
+ supertest = await utils.createSuperTest('role');

If some test resources require an admin role to be created, the test has to instantiate two super test instances. Like here:

   adminSupertest = await utils.createSuperTest('admin');
   viewerSupertest = await utils.createSuperTest('viewer');

[machadoum]

@dmlemeshko @wayneseymour Could you please take a second look?

[wayneseymour]

Just a bit more and I think this will be good.

[wayneseymour]

:LGTM:

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: baf3548

Failed CI Steps

Metrics [docs]

✅ unchanged

History

• 💛 Build #217369 was flaky 09fe39a
• 💛 Build #215705 was flaky a529f78
• 💔 Build #215672 failed d86f1da
• 💔 Build #215236 failed fe033a9
• 💔 Build #215184 failed 667f6cfe2c486f219a9eb2c760ee578e853a36b2
• 💔 Build #214949 failed 093bf5c403a2db083a3b70a02368ecf1954846ca

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @machadoum @tiansivive

[dhurley14]

LGTM!