okta: add configuration options to allow users to make use of httpjson keep-alive options

[efd6]

elastic/beats#34014 will be adding configuration options to httpjson to allow users to specify the behaviour of http keep-alives. This configuration should be made available to integrations that make use of httpjson to perform API requests. A customer has requested that the okta package provide this option to reduce API limit impacts due to the current behaviour that does not allow keep-alives.

Depends: elastic/beats#34014
Depends: elastic/beats#34299
Depends: elastic/beats#34743

[elasticmachine]

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

[andrewkroh]

I think we should make HTTP keepalives enabled in our integrations. That's the optimal behavior IMO. I know that with the httpjson input we did not want to change the behavior because we didn't know who/what would be affected, but with Okta (and other httpjson based integrations) we know how it's being used and we want to optimize the OOTB experience.

[efd6]

Are we never going to be in a situation where resource constraints make this problematic? Would a default enabled be OK or do you specifically want it always enabled?

[andrewkroh]

I was thinking keep-alives on by default, but still toggle-able. I will follow suit with whatever we agree upon in #5483 too.

[efd6]

No worries, I'll invert the default that I have.