Back to source list
Official
Premium
Okta
The CloudQuery Okta plugin extracts data from your Okta domain and loads it into any supported CloudQuery destination
Publisher
cloudquery
Latest version
v6.0.0
Type
Source
Platforms
Date Published
Overview #
Okta Source Plugin
The CloudQuery Okta plugin extracts data from your Okta domain and loads it into any supported CloudQuery destination (e.g. PostgreSQL, BigQuery, Snowflake, and more).
Authentication #
To authenticate CloudQuery with your Okta account you need to set an
OKTA_API_TOKEN
environment variable or add it the configuration.Configuration #
The following example sets up the Okta plugin, and connects it to a postgresql destination:
kind: source
spec:
# Source spec section
name: okta
path: cloudquery/okta
registry: cloudquery
version: "v3.2.13"
tables: ["*"]
destinations: ["postgresql"]
spec:
# Required. Your Okta domain name
domain: "https://<YOUR_OKTA_DOMAIN>.okta.com/"
# Optional. Okta Token to access API
# ⚠️ Warning - Your token should be kept secret and not committed to source control.
# ⚠️ Warning - In the future versions token parameter will become required.
# token: "<YOUR_OKTA_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
, optional)Token for Okta API access. You can set this with anOKTA_API_TOKEN
environment variable.debug
(bool
, optional. Default:false
)Enables debug logs within the Okta SDK.concurrency
(integer
, optional. default:10000
)Number of concurrent requests to be made to Okta API.- Rate limit configuration.
Rate limit spec #
max_backoff
(duration
, optional. Default:5s
)Max backoff interval to be used. If the value specified is less than the default one, the default one is used.max_retries
(int32
, optional. Default:3
)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;