On Tue Nov 10, as part of the university's ongoing transition from Duo to Microsoft multi-factor authentication (MFA), the IP Address Management service will begin using Microsoft MFA for API and alternative (non-SSO) logins. Users not yet enrolled in Microsoft MFA will be able to fall back to Duo until it is decommissioned later this year.
SSO Login using Shibboleth is not affected by this change, already supports Microsoft MFA, and remains the most flexible and convenient way for most users to log into IPAM.
When using the alternative login method, IPAM is not able to prompt you interactively for a second authentication factor, but you can supply both factors at once by appending a comma and a time-based one-time password (TOTP) to your Active Directory password.
- If you do not append anything to your password, you should automatically receive a Microsoft Authenticator push. If that fails, IPAM will try Duo instead, but there may be a noticeable delay.
- If you supply e.g. "password,123456", IPAM will use 123456 as your time-based one-time password (TOTP) for Microsoft MFA.
- If you append e.g. ",push" or a comma and a Duo passcode, this will fail quickly against Microsoft MFA and IPAM will try Duo instead.
- FIDO2 passkeys are not supported by the alternative login method.
Non-person service users already exempted from MFA for IPAM will remain exempted.
Rare edge case: if you currently append e.g. ",push" to the password of your exempted non-person service user (as a placeholder for Duo, following our old suggestion to minimize delay if the actual password happened to contain a comma), you will need to stop appending ",push" and supply only the actual password.
Please contact hostmgr with any questions or feedback.