Okta

The Okta integration in Prelude enables proactive monitoring and alerting specifically for users who lack Multi-Factor Authentication (MFA) and for instances where security policies deviate from Okta’s recommended configurations.

Attaching Okta

To attach a Okta to Prelude SCM, you will need:

  • Base URL of your Okta tenant IE- https://example.okta.com/
  • API User - Username that created the token
  • API Token - API Token generated in Okta portal

Generating Okta API Token

  • Login to okta using a service account with Read Only Administrator role assigned. Prelude performs read operations on the following attributes:
    • User details
    • policies
    • groups
    • UserRisk
  • Navigate to "Security" and select "API"
  • Select "Tokens" tab and then "Create Token"
    • "API calls made with this token must originate from" should be configured to "Any IP"
  • Copy "Token Value" to be used in the Prelude Okta Integration "API Token" field

In Prelude

Attach the partner via UI

  • Navigate to your user name in upper right hand corner and select "Integrations"
  • "Connect to Okta"
  • Fill in Base URL, API User and API token as described above

Detach the partner via UI

    • Navigate to your user name in upper right hand corner and select "Integrations"
  • "Disconnect Okta"