OneLogin
Service ID: onelogin
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- ⚡MODERATEAPI Credentials - Each Consumer Creates a Client ID and Secret in OneLogin
- Authentication
- OAuth 2.0Client credentials grant, using a client ID and secret.
- Partnership Required
- No(Nothing has to be registered with OneLogin to use this connector.)
- Apideck Credentials
- Not available(Each consumer creates their own OneLogin API credentials.)
- Sandbox Availability
- Available(Start a OneLogin free trial to get a test account, then create API credentials in it the same way as in production.)
- Account Type Required
- Any OneLogin account where the consumer can open Developers > API Credentials.
- Consumer Access Level
- A OneLogin account owner or administrator, since only those roles can create API credentials.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enable the OneLogin Connector | ✓ Via Apideck Dashboard | — | — |
| Create the API Credentials in OneLogin | — | ✓ | — |
| Supply the Client ID, Secret & Subdomain in Vault | — | ✓ | — |
| Store & Encrypt Credentials | — | — | ✓ |
| Obtain & Renew Access Tokens | — | — | ✓ |
| Build via the Unified API | ✓ Builds the requests | — | ✓ Maintains connector |
| Monitor Connections | ✓ Via Apideck Dashboard | — | ✓ Logs & alerts |
Environments
- Test and production
- A OneLogin trial is a separate account with its own subdomain and credential pair, so a production connection needs a pair created in the production account. A production connection acts on live user and directory data.
🚨Important to Know About OneLogin
- OneLogin ties API credentials to the user who created them. If that user is later deleted, the credentials fail with HTTP 500 and the consumer must create a new pair and reconnect, so have them create the pair from a long-lived admin account.
📦
1 supported resource
View field mappings, supported operations, and schema details