Last updated April 8, 2019
Organizations that use OneLogin provisioning for user management can integrate that with their StarLeaf account. OneLogin integration is available for organizations on a StarLeaf Enterprise account.
To activate OneLogin integration on your StarLeaf account, contact StarLeaf technical support (firstname.lastname@example.org).
Before you start configuring provisioning for StarLeaf, you need to create an Access token:
- Log in to portal.starleaf.com .
- Go to Integrations > Add integration. Select OneLogin user provisioning and click Apply.
- You see the SCIM server URL and Access token:
- Make a note of the Access token. You will need this when you configure OneLogin. (You do not need to note the SCIM base URL as this is included in the OneLogin integration).
- Log in to OneLogin and select App > Add apps
- Search ‘StarLeaf’ and select the StarLeaf app that appears.
- On the StarLeaf app page, select Save
- Go to Apps > Company apps. StarLeaf is now in the list of your company apps.
- Select the StarLeaf app and then Configuration
- Under SCIM Bearer Token, enter the access token from the StarLeaf Portal.
- Under API Status, select Enable
- Select Save
- Go to Provisioning, and ensure that Suspend is the default selection for when users are deleted in OneLogin, or the user’s app access is removed.
- Select Save.
If you think your access token has been compromised, you must create a new token.
- In the StarLeaf Portal, go to your organization and to Integrations > OneLogin
- Select Regenerate access token
- Select Apply
- Go back to onelogin.com and enter the new token in Apps > Company apps > StarLeaf > Configuration > SCIM Bearer Token
- Select Save
If a user’s Provisioning State is showing as ‘failed’ in OneLogin, the user’s external ID in OneLogin does not match that held by StarLeaf. To fix this: