Server Version 2024.2.9 is not allowing after initial non MFA logon to set DUO "Configure Later" function. Will not allow Username and PW fails with Error wrong username or password.
Login Attempt logs show "Multi-factor user is denied"
Other previous 2024.2.9 admins have MFA\Duo working.
Hello,
Thank you for contacting us on that matter!
Could you please provide us with the following information?
A screenshot of the error message.
Did the problem occur after updating the server to this version?
Do you have more information in the DVLS logs? Here's a helpful topic if needed.
https://docs.devolutions.net/server/web-interface/utilities/reports/logs/
Thank you for letting us know. Your post will be assigned to one of our technicians as soon as possible. If you have any other questions, feel free to let us know.
Best regards,
Maxim Robert
We have not created any new Admin accounts since 2024.2.9 upgrade.

Hello dtech-uma,
Thank you for this feedback.
I have created a user and an admin account with my Duo Authenticator on mobile.
Both of them can connect, but a weird behaviour is that the account related to my Duo is another email, and the MFA is registered under another email.
By using this one, though, I can connect to my Devolutions server without any issues.
Does this issue still occur on the latest version?
Could you tell me if this issue occurs when you connect through the web interface or the client?
Which client are you using?
Could you check the Database logs report?
The login attempt report, too?
Does this admin already have a Duo account configured under his mobile device?
Are you using another method to authenticate?
Does this issue also occur with another MFA-type TOTP?
Have you tried to recreate this user and configure it manually (without the configure later)?
Does this issue still occur if you create him as a user and then switch him to an admin?
Best regards,
Patrick Ouimet