Background
Mio uses encrypted tokens in order to send messages from one platform to another. Occasionally, external changes in a customer’s environment cause tokens to expire. To prepare for these situations, we’ve been hard at work on a solution for uninterrupted chat capabilities.
Auto Heal is Mio's new automation to bridge your organization through token refresh periods.
This article includes a table of situations that would cause Mio to send a prompt, as well as screenshots of the prompts themselves. It is important that admins and end users are aware of these situations, as cross-platform messaging will not work if these prompts are ignored.
Table of contents
How does Auto Heal work?
Mio first detects the external conditions that necessitate token refresh.
Depending on the situation, Mio then automatically sends a notification to either admins or end users requesting re-authorization.
Examples of these conditions include the following:
Situation | Admin Prompt | End User Prompt |
The user or administrator has not consented to use Mio. | Yes | No |
Access has been blocked by Conditional Access policies. The access policy does not allow token issuance. | Yes | No |
Mio has been disabled. | Yes | No |
The user account has been deleted from the directory. | Yes | No |
The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. | No | Yes |
Due to a configuration change made by the administrator, users must enroll in multi-factor authentication. | No | Yes |
The refresh token has expired due to inactivity. | No | Yes |
User account is disabled. | Yes | No |
End user prompt examples
The purpose of the end user prompt is to re-sync secondary platform accounts, similar to when Mio was initially deployed.
End user re-authorization prompts look like this:
Once an end user has re-synced, they will receive confirmation from the Mio bot and are free to continue chatting.
Admin prompt examples
The admin notification is sent in response to a Conditional Access Policy that blocks Mio from obtaining user tokens.
Admins will receive a prompt that looks like this:
After reviewing CAP, admins will receive confirmation that their platform has been successfully configured to work with Mio. After end users respond to the re-authorization prompt, admins will also receive confirmation that a user’s token has been successfully refreshed.
Read more about Mio’s required scopes and permissions on Slack, Webex, Zoom Team Chat, and Teams.