Sign-in Verification
Have requesters prove who they are by signing in to your own Okta or Microsoft Entra ID app before Risotto runs a tool that requires user verification
Sign-in verification lets a requester verify who they are by signing in to your company's own Okta or Microsoft Entra ID app before Risotto runs a tool that requires user verification. Your identity provider's sign-in policy decides how they verify, so the factors you already require, such as passkeys or security keys, apply.
- Stronger factors. A sign-in can require a passkey, a security key, or anything else your identity provider's policy asks for.
- One policy to manage. You set the rules once, in your identity provider, for this app. Risotto follows them.
- The right person, every time. Risotto checks that the person who signed in is the person who made the request.
To watch it end to end, with an Okta app sign-in policy that asks for Okta FastPass before Risotto sends a FileVault key, see the video Example: recover a FileVault key.
Prerequisites
- Okta connected to Risotto. The settings are on the Verification tab of Okta's integration page. Until Okta is connected, the tab shows Okta's connection card instead. See the Okta integration guide.
- Microsoft Entra ID connected too, for an Entra ID app. Risotto looks up each requester in the directory of the app's identity provider. See the Microsoft Entra ID integration guide.
- Access to the same Okta org or Entra tenant. Create the sign-in app in the Okta org or Entra tenant that Risotto is connected to. In another org or tenant, the same person has a different account, so every check fails.
- Requests in Slack or Microsoft Teams. Risotto posts the sign-in link in the requester's own thread. A request with no thread cannot use sign-in verification.
- Org Admin or Manager role in Risotto to change these settings.
Setup
Setup has two parts: an app in your identity provider, then its details in Risotto. Risotto checks the details by having you sign in, and saves them only if the sign-in works.
Step 1: Create the app in your identity provider
Create the app integration
In the Okta Admin Console, go to Applications > Applications and click Create App Integration. Choose OIDC - OpenID Connect, then Web Application.
Configure sign-in
Keep the Authorization Code grant type. Use Client secret for client authentication.
Set the Sign-in redirect URI to the one shown on the Identity verification card in Risotto. Leave the sign-out redirect URIs empty.
Assign users
Under Assignments, assign everyone who might need to verify. Include yourself, because you sign in to test the app.
Copy the credentials
Save the app, then copy its Client ID and Client secret.
Set the authentication policy
Set the app's authentication policy to the factors you want, and to require sign-in every time.
Register the app
In the Microsoft Entra admin center, go to App registrations and click New registration. Choose Accounts in this organizational directory only.
Under Redirect URI, choose Web and enter the sign-in redirect URI shown on the Identity verification card in Risotto.
Copy the IDs and add a client secret
On the app's Overview page, copy the Application (client) ID and the Directory (tenant) ID.
Go to Certificates & secrets, click New client secret, and copy its Value.
Add the auth_time claim
Go to Token configuration, click Add optional claim, choose ID, and add
auth_time. Risotto uses it to check that the requester just signed in.Assign users
In Enterprise applications, open the app. Under Properties, set Assignment required to Yes. Under Users and groups, assign everyone who might need to verify. Include yourself, because you sign in to test the app.
Require sign-in every time
Create a Conditional Access policy for the app with the factors you want, and set Sign-in frequency to Every time.
Step 2: Add the app in Risotto
Open the Verification tab
Go to Settings > Integrations, click Okta, and click the Verification tab. The tab shows the Identity verification card, with short setup steps for your identity provider and the Sign-in redirect URI to copy for step 1. The Verification tab is on the Okta page only, and it shows only when Okta is connected. For a Microsoft Entra ID app, use the same card and choose Microsoft Entra ID as the Identity provider. The Microsoft Entra ID integration page has no Verification tab.
Enter the app details
- Identity provider: Okta or Microsoft Entra ID. The setup steps on the card change to match.
- Issuer:
- Okta: your Okta URL, such as
https://northwind.okta.com. A custom authorization server on the same org also works, such ashttps://northwind.okta.com/oauth2/default. - Microsoft Entra ID:
https://login.microsoftonline.com/<tenant-id>/v2.0, with your directory (tenant) ID.
- Okta: your Okta URL, such as
- Client ID and Client secret: from the app.
Test the sign-in
Click Save and test sign-in. Risotto checks the issuer, then sends you to your identity provider. Sign in as yourself, with the account that has the same email as your Risotto account, within 10 minutes.
You return to the Verification tab, which shows the result. If the test passed, the app is saved and the card shows Verified. If it did not, see Test sign-in results.
Turn it on
Switch on Verify requesters by sign-in. The switch stays off until an app is saved.
Tools that require user verification now ask requesters to sign in instead of sending an Okta Verify push. Requests that were already waiting keep their push.
What requesters see
When a requester asks for something that needs a verified tool, such as a password reset, Risotto posts a message in their thread with a Sign in to verify button. The message names the tool and says when the request expires, 10 minutes after Risotto sent it. In Microsoft Teams, the message is a card with the same button.
The button opens your identity provider's sign-in, which asks them to sign in again with the factors the app's policy requires. A page then tells them the result. When it says You're verified, they can close the tab and go back to Slack or Microsoft Teams.
In the thread, the message changes to Identity verified, and Risotto runs the tool.
While Risotto waits, it posts in the department's agent channel that it is verifying the requester before using the tool, and adds an internal comment to the ticket.
If the sign-in does not verify the requester, the page says why:
- This request is for someone else. A different person signed in. The request keeps waiting for the requester, and the ticket gets an internal comment naming who signed in.
- Sign in again. Your identity provider reused an existing session. The requester can click the same button again until the request expires.
- This request has closed. The verification already finished or expired.
- Something went wrong. The sign-in failed for another reason. The requester can try again from the message.
If the request expires before the requester verifies, the message in the thread changes to "Identity verification did not complete. The IT team will follow up." Risotto does not run the tool and escalates the ticket.
Test sign-in results
After the test sign-in, the Verification tab shows one of these messages. Only a passed test saves the app.
| Message | What it means | What to do |
|---|---|---|
| Test sign-in passed and the app is saved | The app works and is saved | Turn on Verify requesters by sign-in |
| Your identity provider signed you in as a different user than your Risotto account | Your identity provider's account for you is not the one Risotto found for your email | Sign out of other sessions and sign in as yourself. Check that your Risotto email matches your identity provider email, and that the app is in the Okta org or Entra tenant Risotto is connected to |
| Your identity provider did not ask you to sign in again | Your identity provider reused an existing session | Require sign-in every time for the app, then save again |
| Test sign-in failed | Your identity provider refused the sign-in or the app details | Check the issuer, client ID, and client secret, and that you are assigned to the app. For Microsoft Entra ID, also check that the ID token includes the auth_time claim |
| The test sign-in expired | More than 10 minutes passed before you came back | Save again to start a new test |
If the issuer cannot be reached when you save, the form shows the error under Issuer and nothing changes.
Keeping it working
While sign-in verification is off or failing, requesters get an Okta Verify push instead, so a broken app does not block them.
- Rotating the client secret. Create a new secret in your identity provider, enter it in Client secret, and click Save and test sign-in. Sign-in verification stays on with the old secret until the new one passes the test.
- When your identity provider rejects the secret. If the secret expires or is deleted, the first requester sign-in that your identity provider refuses marks the app Failing and adds an alert to the Alerts page. To fix it, save a new client secret and pass the test sign-in.
- Changing the provider, issuer, or client ID. Treated like new details: save, pass the test sign-in, and the new details replace the old ones.
- Turning it off. Switch off Verify requesters by sign-in at any time.
The client secret is stored encrypted and not shown again after you save it. The field then reads "Stored. Enter a new one to replace it."
Limits
- Okta or Microsoft Entra ID only. The app must be in the same Okta org or Entra tenant that Risotto is connected to.
- One sign-in app per org, used for every tool that requires user verification.
- Requests need a Slack or Microsoft Teams thread with the requester. Without one, Risotto cannot send the link and escalates the request to your IT team.
- The requester's email must match exactly one user:
- Okta: one Okta user who is not deactivated, by primary email. An org that matches Slack emails to a different Okta profile attribute is matched by that attribute when no primary email matches.
- Microsoft Entra ID: one user whose mail or user principal name is that email.
- A request expires 10 minutes after Risotto sends it.
Something wrong or missing? Report an issue · View as Markdown