What Oleria discovers
- User accounts and profile attributes synced from New Relic’s account directory.
- Groups and their memberships.
Prerequisites
- Admin access in New Relic with permission to enable SCIM provisioning and generate a SCIM token.
- A New Relic plan that includes SCIM provisioning.
- Admin access on the Oleria platform to add a new integration.
Get your SCIM credentials from New Relic
1
Enable SCIM provisioning in New Relic
Sign in to New Relic as an admin and turn on SCIM provisioning in its admin settings. New Relic may call this user provisioning or directory sync. 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 New Relic 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 New Relic to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations, then select the New Relic 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 New Relic on its regular sync schedule once the initial sync completes.If you regenerate the SCIM token in New Relic, update the Authentication Token in Oleria by editing the integration.
Remediation actions
Oleria can also take these actions in New Relic 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 New Relic.

