User-facing flows of Monofor Identity Client for macOS 2.4.25. Installation and settings: macOS. Problems: macOS Troubleshooting.
Sign in with a QR code
Once the Mac is configured, the login window and the lock screen show the Monofor screen. Scan the QR code with the Monofor Identity mobile app and approve.
Lock screen with the Monofor sign-in
QR code with the tenant logo, account chooser and push button
The QR code refreshes by itself when it expires or after it was used.
A rejected approval shows a message and a new QR code. If the user is not assigned to the application in Monosign, the screen says so.
After the QR code is scanned, the tile shows the Monofor logo until the sign-in finishes.
Sign in with a push notification
Open the Push option and send a notification. When several people use the Mac, choose the account first; the screen shows who the notification goes to. After sending, the button counts down for 15 seconds before another notification can be sent.
Push sent: approve on the phone
While the screen waits for the answer, a Cancel request button is shown (Esc does the same). The notification stays on the phone until it expires; if it is approved later, the cancelled request is ignored.
First sign-in: link or create the Mac account
The first time a Monosign user signs in on a Mac, the client links the Monosign account to a Mac account:
Existing Mac account: the user enters the Mac password once to link it.
No Mac account and Monosign allows local accounts for this user and Mac: the user enters the Monosign password once and the client creates a Mac account with that password. Members of the policy's administrator group become administrators.
Monosign password changed: on the next sign-in the user enters the new Monosign password once and the Mac password is updated.
A Mac account will be created for the user
Sign in with the macOS password
The Monofor sign-in screen has a link Go back to the default Sign-in window. What it does depends on the settings of the administrator:
Default: a password form on the Monofor screen. Enter the Mac account name and password. Passwordless login returns to the QR code.
macOS sign-in screen (from 2.4.25, setting Use the macOS sign-in screen for password sign-in): the screen changes to the sign-in screen of macOS. Sign in there as usual. The Passwordless Login button in the lower left corner returns to the Monofor screen. After a password sign-in, the next lock shows the Monofor screen again.
Password sign-in turned off (from 2.4.25, setting Allow sign-in with the macOS password off): the link is not shown. Use the QR code, a push notification or the offline code.
Offline code
When Monosign cannot be reached (checked every few seconds, not only the network link), the screen switches to the offline code. The last signed-in account is filled in. The code for this Mac is in the Monofor Identity mobile app. After too many wrong codes, offline sign-in is locked until the user signs in online with the QR code.
Offline code entry
Administrator approval
Every macOS administrator prompt (System Settings, installers, saving in the Configurator) opens the Monofor approval window instead of asking for a password. It shows what is being approved and offers QR, Push and Offline code; Command+1 to Command+4 switch between them (Command+4 only when the Touch ID tab is shown). When Touch ID is available for the account, a fourth tab Touch ID appears (see below). A password filled in by the asking app is ignored.
Account not linked on this Mac yet: a macOS password tab is offered next to QR and push, whether Monosign can be reached or not. Administrators can turn this off and require linking first (Configurator setting Offer the macOS password to accounts not linked on this Mac yet).
Linked account: the macOS password is not offered. When Monosign cannot be reached, the offline code is used.
Client not configured (no saved configuration): the prompt hands over to the macOS password.
Saving in the Configurator waits for the approval
Approval window, QR code
Approval window, push sent with the Send again countdown
Approval window, offline code
sudo in Terminal
With Admin prompts and sudo set to Monofor approval, sudo opens the same window. If the user cancels, sudo either asks for the macOS password or fails, depending on the setting If a sudo approval is cancelled, ask for the macOS password.
sudo in Terminal opens the approval window
sudo approval needs Full Disk Access for Identity-Daemon (or the PPPC profile). Only users who may use sudo can approve; for others macOS reports that the user is not in the sudoers file.
Touch ID for administrator prompts and sudo
From 2.4.20 a linked user can approve administrator prompts and sudo with Touch ID. Touch ID is not used at the login window or the lock screen: macOS does not allow third-party login and lock screens to use Touch ID, and after a restart FileVault always needs the password.
The Touch ID tab appears in the approval window when all of these are true:
the console account is linked on this Mac,
Monosign can be reached,
Touch ID is allowed in the Configurator (Allow Touch ID (checked with Monosign each time), on by default),
the Mac has Touch ID with enrolled fingers.
Turn on
In the Touch ID tab press Turn on Touch ID, then approve once with QR or push in the same window. A Secure Enclave key, bound to the current set of fingerprints, is created in the user's session; the daemon stores only the public key.
Each use
The fingerprint signs a random challenge from the daemon.
The daemon verifies the signature.
The daemon checks with Monosign that the account is active, the session is valid and the device is not locked.
Only then is the approval released.
If Monosign cannot be reached, Touch ID is refused: use QR, push or the offline code. An account that is not active, an expired session or a locked device is refused with a message.
Adding or removing a fingerprint makes the key invalid. The user turns Touch ID on again.
Turning on Touch ID and each Touch ID approval are recorded in the Monosign audit log. A Touch ID approval is recorded as USER_LOGIN_SUCCESS with provider TouchID (reason macos_approval_released); a refused Touch ID approval as USER_LOGIN_ERROR_WITH_MFA.
Lock screen after idle
When the Mac locks, the Monofor screen is shown when it is woken. From 2.4.23 this also holds for a Mac that locked by itself while idle: the display lights up for a few seconds right after it went dark, while the client opens the Monofor screen, and then goes dark again.
Remote lock
An administrator can lock the Mac from Monosign. The screen is covered until it is unlocked from Monosign or the user signs in again.









