AlertFind OneLogin Connector

Looking to automate AlertFind Data Import? Yes! This is the place to be. Our OneLogin Connector will make automation a breeze!        

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

1. Region: US or EU.
2. Client ID: This is your API client ID.
3. Client Secret: This is your API client secret.
4. Scope: Gives the credential pair the ability to generate an access token that can perform GET calls available for the User, Role, and Group API resources.
   
   

Note : You can refer to this URL on how to get/generate the API credential pair.

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

• First Name
• Last Name 
• User Name 
• Email 
• Phone 
• Company 
• Department 
• Title
  
  

How does our OneLogin Connector works :

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

Detailed Steps Explaining Above Graphic :

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

Data Storage Nodes in The Graphic Above:

1. Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has 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 log’s 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 and 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.

AlertFind Connector List