EntityAnalytics_Okta: add support for OAuth2 and OIN authentication

[chemamartinez]

Proposed commit message

Added OAuth2 support for the Entity Analytics Okta integration, including the following methods:

• Client secret authentication required for OIN service API authentication.
• JWT-based authentication:
  • JWK file
  • JWK JSON
  • JWK PEM

Note

This PR depends on elastic/beats#45753, CI system tests will fail until it is merged.

Note

Kibana minimum required version has been set to 9.2.0, do not merge this pull request until 9.2.0 is out.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Closes [Entityanalytics_Okta] support for oauth2 and OIN authentication #14931

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: e9868c1

Failed CI Steps

• Check integrations entityanalytics_okta

History

cc @chemamartinez

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!

[chemamartinez]

Reopened: #15668