[okta] Add system tests

[marc-gr]

What does this PR do?

• Adds httpjson system tests for okta package
• Remove log input which only purpose was to have system tests

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.
  - [ ] If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

Related issues

• Relates Move Security integrations to GA #961
• Depends https://github.com/elastic/stream/pulls/23 and to be released as v0.5.0

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #1034 updated

• Start Time: 2021-06-08T09:21:40.385+0000

• Duration: 14 min 23 sec

• Commit: 54a36bb

Test stats 🧪

Test	Results
Failed	0
Passed	12
Skipped	0
Total	12

Trends 🧪

[P1llus]

LGTM, I presume no one would use the logfile input either way here.

[andrewkroh]

I wonder if the new "profile" feature of elastic-package creates an issue here for the hostname. My guess is that it uses a custom docker-compose project name which would break the hardcoded name.

If stream could do a substitution where it reflects back the same hostname used in the HTTP request then that would be more portable. Or if it could substitute in an env var that would work too since it could return the container ID which should be resolvable to the client. For example:

--http-server-response-headers="next=http://{{ RequestAddr }}/api/v1/logs"

--http-server-response-headers="next=http://{{ env 'HOSTNAME' }}/api/v1/logs"

[marc-gr]

/test