In order to perform a successful connection to your Okta instance, we just need the following information and that's it!

  1. Access Token: This token can be found or generated in the settings of the instance using an Admin account.
  2. Okta Domain: Full domain address of your Okta instance.

Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information:

  • Name
  • First Name
  • Last Name
  • Middle Name
  • User Id
  • Mobile Phone
  • Email
  • Secondary Email
  • Title

How does our Okta connector works.

The below graphic explains the various nodes involved in the transition of data from your Okta instance to AlertFind.

Detailed Steps Explaining Above Graphic:

  1. Okta Connector fetches the User information stored in your instance via API.
  2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from Okta instance.
  3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
  4. The CSV is compressed to a Zip file and sent to AlertFind API via AlertFind connector running AWS Lambda.

Data Storage Nodes in Above Graphic:

  1. Node 5: Refers to Apache Cassandra Cluster which stores the data for execution purposes. It as a TTL of 7 days after workflow execution has finished.
  2. Node 6: Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
  3. Data Safety: All data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.

Did this answer your question?