Example: recover a FileVault key (video)
A two-minute example in two parts: an employee locked out of their Mac gets the FileVault recovery key from Iru after a sign-in to Okta, then how to set it up in Risotto and Okta.
One request from start to finish, in two parts. First, what the employee sees: Maya is locked out of her Mac, asks in Slack, proves who she is with a sign-in to Okta, and gets the FileVault recovery key from Iru in a direct message. Then, how to set it up in Risotto and in Okta.
What the employee sees
The employee asks in Slack
Maya's Mac updated overnight, and now it asks for her FileVault recovery key. She's locked out, so she asks in the IT help channel from her phone.
Risotto finds the Mac in Iru
Risotto follows the FileVault runbook. It asks for her serial number, then finds that Mac in Iru, assigned to Maya.
The employee proves who they are
A recovery key unlocks the whole disk, so Risotto checks that it's really her. She taps Sign in to verify, and Northwind's Okta asks for Okta FastPass. The thread changes to Identity verified.
The key arrives by direct message
Risotto gets the key from Iru and sends it to Maya in a direct message, not in the thread. Maya's back in.
How to set it up
In the dashboard, every action is logged on the ticket: the device lookup, the sign-in, the key tool, and that the key went by direct message.
Connect Iru
In Settings > Integrations, open Iru and click Connect on the API token card. Enter your subdomain, an API token that can read device secrets, and your region. See Iru and the Iru FileVault tool's permissions.
Create the runbook from the Iru FileVault template
In Runbooks, click Browse templates, open Iru FileVault Recovery Key Unlock (Simple) and click Use this template. The runbook tells Risotto what to ask and which tools to use. See Runbooks.
Set up the FileVault tool
On the Get FileVault Recovery Key tool, set User Verification to Required, and turn on Send via DM Only. Keep Restrict to Requestor Only on, so the tool only gets keys for devices assigned to the person who asked. Optionally, turn on Requires Approval, so that a person approves before the key is sent. See Get FileVault Recovery Key (Iru) and User verification.
Create the Okta app and its app sign-in policy
In the Okta Admin Console, create an app integration for Risotto: OIDC - OpenID Connect, then Web Application, with the sign-in redirect URI from Risotto. Give the app its own app sign-in policy, with a rule like this one:
- THEN Access is: Allowed after successful authentication
- AND User must authenticate with: Possession factor
- AND Possession factor constraints are: Phishing resistant, which Okta FastPass and passkeys meet
- AND Prompt for authentication: Every time user signs in to resource
Risotto asks for a new sign-in on every request, so the policy must not reuse an existing session. See Sign-in verification.
Turn on sign-in verification in Risotto
Back in Risotto, open Settings > Integrations > Okta and the Verification tab. Enter the issuer, client ID and client secret, click Save and test sign-in, then turn on Verify requesters by sign-in. Now every key needs a fresh sign-in, by the person who asked.
Other device management tools
This example uses Iru. These tools get recovery keys the same way:
- Jamf Pro: FileVault keys. See Jamf Pro and its FileVault tool.
- Fleet: FileVault keys, with the Fleet Get Disk Encryption Key tool.
- Microsoft Intune: BitLocker keys for Windows, with the Get BitLocker Recovery Key tool.
Something wrong or missing? Report an issue · View as Markdown