What Oleria discovers
User accounts and profile attributes synced from Druva’s directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Druva’s standard sync schedule.Prerequisites
- Admin access in Druva with permission to create an API credential.
- Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to Druva’s own API documentation.
Get your SCIM credentials from Druva
1
Create an API credential in Druva
Sign in to Druva as an admin and go to Governance → API Credentials to create a credential for machine access.
2
Copy your SCIM Base URL and Authentication token
Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
- SCIM Base URL - the HTTPS API endpoint for your Druva account.
- Authentication token - the API credential you created.
Copy the credential now. Many applications display it only once. Store it securely and rotate it per your organization’s security policy.
Connect Druva to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the Druva tile.
2
Complete the connection form
Select Continue and fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
Verify the integration
Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs users from Druva on the standard SCIM provisioning schedule once the initial sync completes.If Druva rotates your API credential, update the Authentication token in Oleria by editing the integration.
Governance actions
Oleria can also invoke lifecycle actions in Druva when the credential you provide has write access:- Enable or disable a user account
- Create a new user
Many teams start with a read-only credential for visibility, then grant write access once they’re ready to automate remediation in Druva.