Skip to content

New Source for Okta API #672

Description

@segetsy

There are some good reasons to have a standard component for the Okta API:

  1. Okta SDK is available to handle most of the shared components in a flexible way.
  2. rest_api_source doesn't handle key-based client authentication.
  3. The API is stable, no need to rewrite the resources every time.

Has this been explored before?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Planned

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions