MFA Providers
When a sign-in needs MFA, AuthNull sends a push to the user's phone through your organization's MFA provider. AuthNull supports:
| Provider | Push app | Best for |
|---|---|---|
| AuthNull Authenticator (iOS and Android; macOS and Windows coming soon) | Organizations without Duo or Okta, or that want no external service | |
| Duo Mobile | Organizations that use Duo | |
| Okta Verify | Organizations that use Okta |
One provider is active per organization, and it is used for every product: Identity, Database, RADIUS, and PAM.
Choose a Provider
Open the account menu (top right), choose Settings, then MFA Provider, and select a provider card. Only one provider can be active: once Duo Security or Okta Verify is saved, the other card shows Remove the active provider to switch.
AuthNull Authenticator
Select the AuthNull Authenticator card. There are no credentials to enter: the app talks to AuthNull directly. Then invite users from Users → ⋯ → Register device, or use Invite everyone who isn't set up yet on the same page. See Authenticator Admin Setup for invites and device settings.
Duo Security
Enter the details of your Duo application:
| Field | Example |
|---|---|
| API hostname | api-XXXXXXXX.duosecurity.com |
| Integration key | DI... |
| Secret key | Your Duo secret key |
Users must be enrolled in Duo Mobile before you enforce MFA.
Okta Verify
Enter your Okta organization's details:
| Field | Example |
|---|---|
| Okta org URL | acme.okta.com |
| API token | An Okta API token (00T...) |
Users must have Okta Verify enrolled in your Okta organization.
AuthNull finds each user in Duo or Okta by email address. A user's email in AuthNull must match their Duo or Okta account, or the push cannot be delivered.
When you edit a saved provider, leave the secret fields blank to keep the stored values.
Provider Status
| Status | Meaning |
|---|---|
| Active | Configured for this organization; credentials are stored encrypted per organization |
| Deployment default | Not configured for this organization - inherited from the deployment's default setting |
| Incomplete | Saved, but some required details are missing |
With Duo Security or Okta Verify, users on the Users page show MFA managed by that provider: their second factor is enrolled there, not in AuthNull. With the AuthNull Authenticator, each user's enrolled devices are managed from Users → ⋯ → Register device.
How Users Sign In to the Console
Signing in to the AuthNull console itself uses a password plus a second factor - an authenticator app code (TOTP), a passkey, or a push. See End-User Console Access.