Azure AD Users May Be Unable to Authenticate to Frame or Receive New Persistent Desktop / User Volume

Final update

An update to a backend SAML2 library resulted in XML Namespaces being improperly stripped from Azure AD SAML2 claims. This resulted in some users being unable to authenticate as Frame was unable to properly match these claims in order to establish user identify. Users who were able to authenticate may have improperly received a new Persistent Desktop and/or User Volume (Enterprise Profile or Personal Drive) upon starting a session. This issue seems to only affect customers on our Frame Commercial Platform using Azure AD via SAML2 integration with Frame. This issue was first reported at 1:15AM PDT and was resolved by 5:15AM PDT on Thursday, May 12, 2022.

1. Resolved · May 12, 08:15 UTC
   An update to a backend SAML2 library resulted in XML Namespaces being improperly stripped from Azure AD SAML2 claims. This resulted in some users being unable to authenticate as Frame was unable to properly match these claims in order to establish user identify. Users who were able to authenticate may have improperly received a new Persistent Desktop and/or User Volume (Enterprise Profile or Personal Drive) upon starting a session. This issue seems to only affect customers on our Frame Commercial Platform using Azure AD via SAML2 integration with Frame. This issue was first reported at 1:15AM PDT and was resolved by 5:15AM PDT on Thursday, May 12, 2022.