Need Help? We are right here!
Thanks for your Enquiry.
If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com
Search Results:
×Set which 2FA methods are available across your organization and whether they're required.
This is where an admin decides which 2FA methods are available to users, whether 2FA is mandatory for dashboard login, and whether users configure their own method or use the admin's.
Note: This page controls 2FA for dashboard login. If you want two-factor authentication when a user opens a specific resource instead, skip to Requiring MFA on Specific Resources below to enable that option.
Allowed Methods only shows four methods, already turned on: Google Authenticator, Microsoft Authenticator, Authy Authenticator, and FIDO2 (Biometric). These need no external account or credentials.

Every other method - SMS, Email, Call Verification, Miniorange Authenticator (Push Notification, QR Code, Soft Token), Security Question, and Hardware Token (Yubikey) - stays hidden until you connect a miniOrange IAM account and turn that integration on. See the two-step groups below.



https://branding.xecurify.com/moas) of your miniOrange account, then click Save.


Note: These credentials belong to an existing miniOrange IAM account - this panel doesn't create one for you. Once saved, the fields lock and the password is masked. There's no separate Connect or Test Connection step; Save is the only action.


Note: The Cool Down Period is an organization-wide setting; there's no per-device remember this device option.
If you're the primary admin, a switch labeled Apply Admin's Two-Factor Authentication Methods to PAM Users appears. Turning this on enforces your configured method for every user - they'll no longer configure their own method and will authenticate using your credentials/method instead.

Note: This can't be used with QR Code Authentication, Yubikey Token, Security Question, or FIDO2 as your method - configure a compatible method first.

2FA on dashboard login is separate from MFA on individual resources. If you want two-factor authentication when a user opens a specific resource instead:

Refer to the Policies section of this handbook for full details on creating and assigning policies.