Skip to main content
Archer is a governance, risk, and compliance (GRC) platform for managing organizational risk programs. Connect your Archer account to Oleria to bring user and group access into your identity and access graph.

What Oleria discovers

  • User accounts and profile attributes synced from Archer’s directory.
  • Groups and their memberships.
Oleria uses this data for dormant account detection and access reviews, refreshed on Oleria’s regular sync schedule.

Prerequisites

  • An Archer SaaS instance. Archer offers SCIM only on SaaS.
  • The Archer SCIM service, purchased as part of Archer Evolv or as a standalone service. SCIM isn’t enabled by default.
  • Admin access on the Oleria platform to add a new integration.

Get your SCIM credentials from Archer

1

Request SCIM activation from Archer Technical Support

Raise a SCIM service activation request with Archer Technical Support. Include your customer account name, instance IDs, the instance type (production or non-production), the URL of your Archer SaaS instance, the identity provider you’ll connect, and a contact person.
2

Receive your SCIM Base URL and API key

Archer shares two values with your contact person. You’ll paste them into Oleria in the next section:
  • SCIM Base URL - your instance’s SCIM host. For example, if your Archer URL is https://xyz-prod.archerirm.com, the SCIM Base URL is https://xyz-prod.scim.archerirm.com.
  • API Key - the credential that authenticates SCIM requests.
Archer’s SCIM guidance is to use one SCIM application per Archer instance and not to reuse a SCIM application across environments or instances. Archer doesn’t document whether a second SCIM client, such as Oleria, can share an instance’s SCIM Base URL and API key. If your identity provider already provisions Archer through SCIM, confirm with Archer Technical Support before you connect.

Connect Archer to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Archer 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 Archer on its regular sync schedule once the initial sync completes.
If Archer issues you a new API key, update the Authentication Token in Oleria by editing the integration.

Remediation actions

Oleria can also take these actions in Archer:
  • Enable or disable a user account
  • Add or remove a user from a group
  • Create a new user or group
Archer recommends that you create and configure groups manually in Archer instead of through SCIM. A group created through SCIM isn’t linked to any role, so it grants no permissions until an Archer administrator configures it. Create groups in Archer, then use Oleria to add and remove members.
Oleria doesn’t check the API key’s permissions until an action runs.

Known limitations

  • Archer’s SCIM service doesn’t support nested groups or groups with duplicate names.

Contact us

For questions about this integration, contact us at support@oleria.com.