[docs] Filebeat Entity Analytics Okta - add additional API interactions

[andrewkroh]

The documentation for the Entity Analytics input should be updated to mention additional Okta API interactions for

beats/x-pack/filebeat/input/entityanalytics/provider/okta/internal/okta/okta.go

Line 268 in 6a467e2

const endpoint = "/api/v1/users/{user}/groups"

beats/x-pack/filebeat/input/entityanalytics/provider/okta/internal/okta/okta.go

Line 290 in 6a467e2

const endpoint = "/api/v1/groups/{group}/roles"

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[efd6]

The current documentation is technically correct. Okta considers the APIs to be named at the third path level. We do reach into lower levels of the API to get roles and groups, but those are essentially boring implementation details. The main importance of the list of APIs is what rate limiting is in place, and this is determined at the API name level, not the endpoint level. I can add the additional information, but I think it will be more confusing than helpful.

Note that GetGroupRoles is not currently called, so /api/v1/groups/ is never touched by us (this may change in the future).

[andrewkroh]

I trust your judgment if you think it might be more confusing than helpful. This request was primarily for my own benefit anyway. Instead of going to the code, as a shortcut during a meeting, I was trying to use the docs to reverse-engineer which API calls the provider was capable of.