Skip to content
  • There are no suggestions because the search field is empty.

Integrations : SSO Logs : Okta

Adding the Okta Integration and Its Associated Insights

Overview

The Okta – System Logs connection in Block 64 enables secure, read-only access to your Okta system logs.

This integration provides visibility into authentication events, application activity, and other identity-related events for your organization.

Because this is a customer-managed connection, you control how the integration is configured and the level of access granted.

Once connected, the data collected from this integration appears in the following Block 64 Insights report:

  • Reports → SaaS → Usage

    • Displays Okta login activity, authentication events, and usage trends across your environment.

The credentials needed for this Integration

To set up this integration, you’ll need the following from your Okta Admin Console:

  • An Okta administrator account with permission to create applications and assign the necessary API scopes for system log access.

  • Client ID – Generated when you create the Okta application for Block 64.

  • Client Secret – Generated alongside the Client ID; required for authentication.

  • Okta Domain – Your organization’s Okta domain in the format yourcompany.okta.com.

How to add this Integration

  1. Review the setup guide here: Block 64 Connection for Okta System Logs.

  2. In your Okta Admin Console:

    • Create an Okta application for Block 64 following the guide.

    • Generate a Client ID and Client Secret for the application.

    • Note your Okta domain (e.g., yourcompany.okta.com).

  3. In the Block 64 portal, go to Integrations → Okta – System Logs.

  4. Enter the following details:

    • Client ID – from the Okta application you created.

    • Client Secret – from the Okta application you created.

    • Domain – your Okta domain in the format yourcompany.okta.com.

  5. Click Connect to finalize the setup.

Why is this Integration failing?

If the integration isn’t working, it’s often due to one of the following:

  • Incorrect credentials – The Client ID, Client Secret, or Domain entered in Block 64 does not match the values in your Okta application settings.

  • Expired or revoked credentials – The Client Secret may have been regenerated in Okta without updating it in Block 64.

  • Insufficient permissions – The Okta application may not have the required scopes to access system logs.

  • Domain format issues – The domain must be entered in the format yourcompany.okta.com without https:// or extra characters.

To fix this:

  1. Re-check the Client ID, Client Secret, and Domain entered in Block 64.

  2. Verify the Okta application is active and has the required API scopes for system logs.

  3. If you regenerated the Client Secret, update it in Block 64 immediately.

  4. Test the integration connection after making changes.

How to remove this Integration

From Block 64:

You can disable this integration temporarily by clicking on the Enable switch in the integration.

Alternatively, you can disconnect the integration entirely by clicking on the Disconnect button.

From Okta:

  1. Sign in to the Okta Admin Console.

  2. Go to Security → API → Tokens.

  3. Locate and delete the API token used for the Block 64 integration.