Okta

On this page

Okta Log Events is a Security input connector. Connect to Okta and retrieve Identity events. Create an Okta API token to get started.

IP Allowlists

You might need to add the Monad IP range of 34.210.32.104/32 to your Okta allowlist, so Monad can connect to it.

Create a Okta API token

Before you connect Monad to Okta, you need an API token. API tokens are scoped to include all projects from a specific account in Okta.

Instructions Here.

Get your Okta organization name

In most cases, your organization name is simply your company name. However, you can also extract the organization name from your url.

  1. Go to the Okta admin dashboard.
  2. Extract your Okta org name from your url. If your url is https://companyname-admin.okta.com/admin/dashboard then your org. name is companyname. There are some slight variations on the Org. URLs so it could be that your URL could be https://companyname.okta.com or https://companyname.okta-emea.com. Still your org name in those cases would be companyname.

More details and edgecases mentioned here.

Set up a Okta input connector in Monad

To set up a Okta connector, you need an API token. Once you have this information, you set up the connector:

  1. Log in to your Monad account, and click Add connector.
  2. Select the Okta connector.
  3. Optionally, change the default name for the connector. This name serves as a label for the connector in the Monad app, and you can change it later.
  4. Enter the Okta organization name.
  5. Enter the API token you created.
  6. (Optional) - set your connector schedule
  7. Click Connect.

That’s it! Monad tests the connection to Okta. If the account is configured correctly, you’re ready to pull your Okta data into Monad!

This page was last modified: 9 Oct 2023