What Oleria discovers
- User accounts and profile attributes synced from incident.io’s directory.
- Groups and their memberships.
Prerequisites
- Admin access in incident.io with permission to enable SCIM provisioning and generate a SCIM token.
- An incident.io plan that includes SCIM provisioning.
- Admin access on the Oleria platform to add a new integration.
Get your SCIM credentials from incident.io
1
Enable SCIM provisioning in incident.io
Sign in to incident.io as an admin and turn on SCIM provisioning in Settings > SCIM. Then generate a SCIM token.
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 SCIM 2.0 endpoint incident.io shows when you enable provisioning.
- Authentication Token - the SCIM bearer token.
Copy the token now and store it securely. Rotate it per your organization’s security policy.
Connect incident.io to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the incident.io 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.
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 incident.io on its regular sync schedule once the initial sync completes.If you regenerate the SCIM token in incident.io, update the Authentication Token in Oleria by editing the integration.
Remediation actions
Oleria can also take these actions in incident.io 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 SCIM token’s permissions until an action runs. If an action fails, confirm the SCIM token can update users and groups in incident.io.