Skip to main content
FireHydrant is an incident management platform. Connect your FireHydrant account to Oleria to bring user and team access into your identity and access graph.

What Oleria discovers

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

Prerequisites

  • A FireHydrant account on the Enterprise plan.
  • The Owner role in FireHydrant.
  • Admin access on the Oleria platform to add a new integration.

Get your SCIM credentials from FireHydrant

FireHydrant’s SCIM API authenticates with a FireHydrant API key. An API key has Owner permissions by default, so create a dedicated key for Oleria.
1

Create an API key

In FireHydrant, go to Settings > API Keys and select + Create API key. Enter a name and description, then select Save.
FireHydrant shows the key only once. Copy it now and store it securely.
2

Note your SCIM Base URL

Use the SCIM base URL for your FireHydrant region:
  • US: https://api.firehydrant.io/v1/scim/v2
  • EU: https://api.eu.firehydrant.io/v1/scim/v2

Connect FireHydrant to Oleria

1

Open the integration

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

Remediation actions

Oleria can also take these actions in FireHydrant:
  • Enable or disable a user account
  • Add or remove a user from a group (team)
  • Create a new user
Disabling a user in FireHydrant removes them from all current and future on-call shifts, on-call rotations, and escalation policy steps that target them directly. It also disables alert rules that target them. Enabling the user again, or reverting the action, doesn’t restore any of these, so you must set them up again in FireHydrant.
Oleria doesn’t check the API key’s permissions until an action runs.

Known limitations

  • All FireHydrant accounts in a region share one SCIM host, so each Oleria workspace can have one FireHydrant connection per region.
  • FireHydrant rate limits requests made with bot tokens per account, so every bot token in the account shares one limit. FireHydrant’s API takes bot tokens, so if your identity provider uses a FireHydrant API key, it shares the limit with Oleria’s key.

Contact us

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