Security
Send Okta alerts to on-call with CallHeim.
Okta Event Hooks reach CallHeim through a small relay you run, which answers Okta’s one-time verification request and forwards each delivery. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.
Needs a forwarder
Okta does not post to CallHeim on its own for this. You set up a forwarder, rule or script that sends the event to your CallHeim URL; the setup steps show what to send.
Setting it up
Okta verifies a new Event Hook with a one-time GET request, and CallHeim’s ingest URL accepts POST only. Run a small relay (for example a Cloud Function or Lambda) that answers the verification request and forwards each delivery to your CallHeim integration URL. Each event in a delivery becomes its own alert.
Create an Integration in CallHeim and choose Okta from the Catalog to get its ingest URL, and use that URL as the target of your forwarder. CallHeim’s ingest URL takes a JSON request body. The snippet beside this shows the request it expects, with {{WEBHOOK_URL}} replaced by your real URL.
Okta cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.
CallHeim includes a payload mapping for Okta’s webhook format.
# Registering an Okta Event Hook requires answering a one-time GET verification
# challenge. CallHeim’s ingest endpoint accepts POST only, so run a relay that answers
# the challenge and forwards events to your CallHeim integration URL.After it arrives
What CallHeim does with Okta alerts.
A repeat of the same finding attaches to the incident already open for it, and an Orchestration Rule can route findings by severity, title or any payload field to the team that owns them.
CallHeim maps Okta’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →
Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →
The thresholds it passes through
- Repeat, sender-supplied dedup key
- attaches, any age
- Repeat, title or subject only
- attaches, incident under 24 h old
- Flap threshold
- 4 transitions / 600s
- Title correlation
- similarity ≥ 0.6, same source and service
- Group window default
- 600s
All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →
Point Okta at CallHeim and see what it does with your alerts.
Start on the free trial, connect Okta and send a test alert to see the incident it opens.