SSO on ActiveDirectory in combination with TOTP-2FA not working (DVLS 2025.3.7.0)
Hello members of the Devolution community,
last friday i tried updating out DVLS to version 2025.3.7.0 and after a successful installation of the update SSO with MFA stopped working. For MFA we are using TOTP with Microsoft Authenticator on our smartphones in combination with Micrsoft Active Directory. I rolled back the update without any further diagnostics.
Today i tried to reproduce this issue on our test enviroment (with version 2025.3.7.0 of DVLS) and SSO without MFA works. After enabling MFA in combination with SSO i was able to reproduce the issue. Since SSO without MFA works i assume that the issue has to be somewhere near the MFA and our Domain-Configuration is not the cause of this problem.
I got the following message form the DVLS-Console logs:
Cookie user '"<username - censored>"' attempted to login as '""' from IP "<client ip - censored>"
I also included the DVLS-Log with Debug-messages in attachments.
Please take a look at this issue and if you need further information let me know.
Greetings from Germany,
Markus
DVLS_Log_censored.txt
Hello Markus,
Thank you for your post and for the effort you put into troubleshooting the bug. We are aware of this behavior, and our development team is currently working on a fix. It will be included in version 2025.3.8, which is expected to be released between today and tomorrow.
Thank you for your patience. I will keep you updated.
Best regards,
Michel Audi
Hello Michel,
thank you for your fast response. Glad you are already aware of this issue. I am looking forward for the update.
Best regards,
Markus
Hello Markus,
Thank you for your post and for the effort you put into troubleshooting the bug. We are aware of this behavior, and our development team is currently working on a fix. It will be included in version 2025.3.8, which is expected to be released between today and tomorrow.
Thank you for your patience. I will keep you updated.
Best regards,
@Michel Audi
Seems like the 2025.3.8 is out. When can we expect the fixed "stable" version?
Hello @villepeltola,
The stable version which includes the fix is already available.
Regards,
Min