Set up process #

Okta Source Plugin

Authentication #

Configuration #

kind: source
spec:
  # Source spec section
  name: okta
  path: cloudquery/okta
  registry: cloudquery
  version: "v5.5.0"
  tables: ["*"]
  destinations: ["postgresql"]
  # Learn more about the configuration options at https://cql.ink/okta_source
  spec:
    # required, Okta domain name, for example: https://example.okta.com, https://example.okta-emea.com,  https://example.oktapreview.com
    domain: "${OKTA_DOMAIN}"
    # required, Okta Token to access API
    token: "${OKTA_ACCESS_TOKEN}"

    # Optional. Rate limiter settings
    # rate_limit:
    #   max_backoff: 5s
    #   max_retries: 3

• domain (string) (required)

  Specify the Okta domain you are fetching from. Visit this link to find your Okta domain.
• token (string) (required)

  Token for Okta API access.
• debug (bool) (optional) (default: false)

  Enables debug logs within the Okta SDK.

  This feature will result in sensitive information being logged!
• concurrency (integer) (optional) (default: 10000)

  A best effort maximum number of Go routines to use. Lower this number to reduce memory usage.
• scheduler (string) (optional) (default: dfs) The scheduler to use when determining the priority of resources to sync. Supported values are dfs (depth-first search), round-robin, shuffle and shuffle-queue.

  For more information about this, see performance tuning.
• rate_limit (Rate limit spec) (optional) (default: see rate limit spec defaults)

  Rate limit configuration.

Rate limit spec #

• max_backoff (duration) (optional) (default: 30s)

  Max backoff interval to be used. If the value specified is less than the default one, the default one is used.
• max_retries (integer) (optional) (default: 2)

  Max retries to be performed. If the value specified is less than the default one, the default one is used.

Example Queries #

List all users in Okta #

select 
  id,
  profile->>'firstName' as first_name,
  profile->>'lastName' as last_name,
  profile->>'email' as email,
  status
from okta_users;

List all active users #

select
  id,
  profile->>'firstName' as first_name,
  profile->>'lastName' as last_name,
  profile->>'email' as email,
  status from okta_users
where
  status = 'ACTIVE';

List active Okta applications #

select
  id,
  name
from
  okta_applications
where status = 'ACTIVE';

List active Okta applications, ordered by number of users #

select 
  a.id,
  a.name,
  a.status,
  count(u) 
from okta_applications a 
  left join okta_application_users u 
    on u.app_id = a.id 
group by a.id, a.name
order by count desc;