Skip to lesson
Exit
Identity & Access Deep Dive1 / 3

1 min lesson

Leaver

Explain the order in "Leaver", then say how you would verify the result.

Step 1 of 3

Leaversame-second, fully audited

  1. 1Trigger. HRIS marks termination; for involuntary exits, support an immediate manual override that fires now.
  2. 2Deactivate identity. Disable the IdP account, which cascades SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. deactivation to every connected app.
  3. 3Catch the non-SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. apps. Script-based deprovision for anything without SCIM, so there's no manual gap.
  4. 4Handle the device. MDM lock or remote wipe and reclaim the hardware.
  5. 5Write the audit record. Log what was revoked, when and by what trigger. That record is your offboarding evidence for SOC 2.
Learn more

Full explanation

Engineering the pipeline well

Engineering the pipeline wellwhat makes it production-grade

  • Idempotent. Re-running a leaver event on an already-offboarded user is a no-op, never an error, because events get redelivered.
  • Retried with backoff. A downstream API being down can't drop a deprovision; queue it, retry and alert if it stays stuck.
  • Audited end-to-end. Every action emits a record: who, what, when, triggered by which HRIS event.
  • Alerted on failure. A silent deprovision failure is the worst outcome, so page on it.
  • Version-controlled. The mappings and workflow logic live in Git, reviewed like any other code.
Say it like this

"HRIS is my source of truth. A leaver event disables the IdP account, which cascades SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. deactivation across every connected app; a script handles the non-SCIM stragglers; MDM wipes the device; and the whole thing writes an audit record. It's idempotent and retried, so a redelivered event or a flaky API never leaves a live credential behind."

Learn more

Optional practice

Test yourself on Leaver

QIn a JML pipeline, why is the Mover case the most commonly botched and how do you design it correctly?

Learn more

Optional practice

Test yourself on Leaver

QWhy must the leaver workflow be idempotent and what does that mean concretely?