Skip to content

[ux-design-patrol] Fix Okta role-permissions API endpoint in entity analytics docs #49964

Description

@github-actions

docs/reference/filebeat/filebeat-input-entity-analytics.md has a user-facing API endpoint inconsistency introduced in commit c76211f2ff09e2dfe4b8fec45996b0ed65821655.

Evidence:

  • Current docs (lines 968-970, blamed to c76211f2ff0):
    • `* [/api/v1/iam/roles]((developer.okta.com/redacted)
  • Implementation and tests use role-permissions endpoint:
    • x-pack/filebeat/input/entityanalytics/provider/okta/internal/okta/okta.go:347
    • const endpoint = "/api/v1/iam/roles/{roleId}/permissions"
    • x-pack/filebeat/input/entityanalytics/provider/okta/okta_test.go:164 also targets /api/v1/iam/roles/{roleId}/permissions

Why this is UX drift:

  • Nearby endpoint bullets in this same section list exact API paths being called (/api/v1/users, /api/v1/devices).
  • The new bullet switched to a broader path (/api/v1/iam/roles) while describing permissions enrichment, which is inconsistent with actual behavior and can mislead users configuring scopes/troubleshooting calls.

Suggested consolidation:

  • Update that bullet to [/api/v1/iam/roles/{roleId}/permissions](...) and keep the same endpoint-specific style as adjacent bullets.
  • (Optional wording polish) It also reads role permissions... for grammar clarity.

Note

🔒 Integrity filtering filtered 123 items

Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

  • #49658 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49163 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49099 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #39761 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #44780 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #39352 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49851 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49850 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49849 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49511 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49796 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49848 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49699 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49701 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49700 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • #49518 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
  • ... and 107 more items

What is this? | From workflow: UX Design Patrol

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

  • expires on Apr 14, 2026, 1:41 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs_teamIndicates that the issue/PR needs a Team:* label

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions