OneLogin
Events
Fetches events data from a OneLogin account.
Sync Type: Incremental
Requirements
- Before you connect Monad to OneLogin, you need client credentials.
- Instructions Here.
- Get your OneLogin Subdomain, and is of the format domain.onelogin.com, which is also a part of the URL you would access your account with.
- In most cases, your subdomain name is simply your company name. However, you can also extract the subdomain from your url.
Details
Monad uses the since query parameters on the API to determine what events to display. This field is updated every time a request to get events is successful with the time of the latest event generated. If this was the first time requesting for events, a full sync of the data is performed.
Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.
Settings
| Setting | Type | Required | Description |
|---|---|---|---|
| Subdomain | string | Yes | Your organization's specific OneLogin domain. Typically is of the format domain.onelogin.com. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| Client ID | string | Yes | ClientID to authenticate with the OneLogin API. |
| Client Secret | string | Yes | ClientSecret to authenticate with the OneLogin API. |
Sample Record
Code
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.
Last modified on