A bug in the WS-Federation protocol handler caused Office 365 Federated SSO to stop working properly

Features & Improvements

Version 6.5.2.0601 (June 01, 2022)

...

Upgrading failed with SQL error when Dualshield is connected to an MS-SQL 2014 server (3757)
IIS apps, e.g. OWA, got the error "Invalid SAML Response: Signature verified failed" after upgrading to DualShield 6.5.1 (3750)
When signing in from a new device with an Outlook client, it doesn't trigger the device registration alert
Cross-origin resource sharing: arbitrary origin trusted (3730)
Logon request timed out in OOBA call in a system with 2 or more Dualshield backend servers (3734)
The option InResponseTo was not functional and the attribute was always included in the SAML response (3484)
Extra 'S' in the SSO URL after using the change FQDN feature to change the HTTP protocol (3658)
Failed to generate the SAML response when both assertion and response are ticked for signature (3699)
Did not include ClientIP in intrusion alert (3713)
Import a full-chained certificate gets the error: Certificate not chained (3745)
Assigning token in DAC got null pointer exception (3746)
False error messages in das6.log: "The application's global logon procedure is not found: Desktop SSO" (3751)
The DualShield Service Console displays Error 404 when the user has no permission in Token and Account in the Self Service Policy (3754)
Reset token successfully but there is no confirmation on the screen at all (3756)

Support WSFED for Outlook Web Access (OWA) and EAC (Exchange Access Console) (3758)
Support multiple values of a SAML attribute (3648)
Querying nested group membership took long time when checking roles and license (3709)
New task for pushing MobileID download link in bulk by user group or domain (3718)

...