The CloudQuery Okta plugin extracts data from your Okta domain and loads it into any supported CloudQuery destination
Publisher
cloudquery
Latest version
v6.6.1
Type
Source
Platforms
Date Published
Loading plugin documentation
We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
token or client_id and private_key properties in the sync configuration.\\n) to avoid PEM decoding errors. For example:export OKTA_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\\nMIIEv.....giKW1k=\\n-----END PRIVATE KEY-----"
kind: source
spec:
# Source spec section
name: okta
path: cloudquery/okta
registry: cloudquery
version: "v6.6.1"
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 when using client credentials authentication
client_id: "${OKTA_CLIENT_ID}"
private_key: "${OKTA_PRIVATE_KEY}"
# required when using token authentication, Okta Token to access API
token: "${OKTA_ACCESS_TOKEN}"
# Optional. Rate limiter settings
# rate_limit:
# max_backoff: 5s
# max_retries: 3
domain (string) (required)token (string) (optional)client_id (string) (optional)private_key (string) (optional)debug (bool) (optional) (default: false)concurrency (integer) (optional) (default: 10000)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.max_backoff (duration) (optional) (default: 30s)max_retries (integer) (optional) (default: 2)select
id,
profile->>'firstName' as first_name,
profile->>'lastName' as last_name,
profile->>'email' as email,
status
from okta_users;
select
id,
profile->>'firstName' as first_name,
profile->>'lastName' as last_name,
profile->>'email' as email,
status from okta_users
where
status = 'ACTIVE';
select
id,
name
from
okta_applications
where status = 'ACTIVE';
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;
kind: source
spec:
name: okta
path: cloudquery/okta
registry: cloudquery
version: "v6.6.1-fips"
...