To ship Okta logs, you’ll deploy a Docker container to collect the logs and forward them to Logz.io.

Configuration

Before you begin, you’ll need: Okta administrator privileges

Get the API token and issuer URI from Okta

In the Okta developer console, navigate to API > Tokens. Create a token and paste it in your text editor.

Create Okta API token

Click the Authorization Servers tab. Copy your Okta subdomain from the Issuer URI column, and paste it in your text editor.

Okta URL

In the example above, you’d have copied “dev-123456”.

Pull the Docker image

Download the logzio/docker-collector-logs image.

docker pull logzio/docker-collector-logs
Run the Docker image

For a complete list of options, see the parameters below the code block.👇

--detach \
--restart always \
--name Okta \
--env LOGZIO_TOKEN=<<SHIPPING-TOKEN>> \
--env LOGZIO_LISTENER_HOST=<<LISTENER-HOST>> \
--env OKTA_API_KEY=<<OKTA-API-KEY>> \
--env OKTA_TENANT=<<OKTA-ISSUER-URI>> \
-t logzio/logzio-okta
Parameters
Parameter Description
LOGZIO_TOKEN Your Logz.io account token. Replace <<SHIPPING-TOKEN>> with the token of the account you want to ship to.
LOGZIO_LISTENER_HOST Logz.io listener URL to ship the logs to. Replace <<LISTENER-HOST>> with your region’s listener host (for example, listener.logz.io). For more information on finding your account’s region, see Account region.
OKTA_API_KEY The Okta API key you copied in step 1.
OKTA_TENANT The Okta issuer URI you copied in step 1.
Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Kibana.