What Oleria discovers
User accounts and profile attributes, and Lucid organizational groups with their members, synced from Lucid’s SCIM API. Oleria uses this data for access reviews, refreshed on Oleria’s regular sync schedule.Prerequisites
- A Lucid Enterprise account. Lucid offers SCIM only on Enterprise. Lucid says the base URL can be different for accounts in its FedRAMP environment. If your account is there, contact us before you connect, so we can confirm Oleria can reach that URL.
- An account owner or account admin in Lucid, to generate the SCIM bearer token.
- Admin access on the Oleria platform to add a new integration.
Get your SCIM credentials from Lucid
Lucid has two SCIM integrations, and each has its own bearer token. Use SCIM for admin management: with its token, Lucid’s SCIM API returns your users and your Lucid organizational groups. A SCIM for content access token returns Lucid teams instead.1
Open SCIM for admin management
Sign in to Lucid as an account owner or account admin. Select Admin, then App integration. On the SCIM for admin management tile, select Settings (or Install).
2
Generate your Authentication Token
In the bearer token section, select Generate token, and copy the token. You’ll paste it into Oleria in the next section.
Lucid says that with SCIM for admin management you may need to turn on Auto-purchase licenses in Lucid, so that provisioning can license and de-license users automatically.
Connect Lucid to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the Lucid tile.
2
Complete the connection form
Fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
A token works only with the integration it was generated for. Oleria identifies a Lucid connection by its base URL, which is the same for every Lucid account, so you can connect one Lucid account, with one integration’s token, per Oleria workspace.
Verify the integration
Confirm the new instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. Oleria syncs users and groups from Lucid on its regular sync schedule once the initial sync completes.If you regenerate the SCIM token in Lucid, update the Authentication Token in Oleria by editing the integration.
Remediation actions
Oleria can also take these actions in Lucid when the SCIM token can update users and groups:- Enable or disable a user account
- Add or remove a user from a group
- Create a new user or group
Oleria doesn’t check the token’s permissions until an action runs. If an action fails, confirm the token can update users and groups in Lucid.
Known limitations
- Lucid doesn’t document whether its SCIM API lists deactivated users. If it doesn’t, a user deactivated (by Oleria or in Lucid) drops out of Oleria’s inventory after the next sync and can’t be selected for Enable. To re-enable a user Oleria disabled, an Oleria administrator can select Undo on that disable action in Action Center within 7 days. After that, re-enable the user in Lucid.
- A Lucid user can belong to only one organizational group.

