![]() ![]() In parallel, I also created a support ticket to Microsoft, and for my first time tested to use the Enable “ advanced diagnostics.” We verified that there were not any changes done with the SAML library or Claims, before I started sending the SAML logs. I also had dialog with the 3.party application vendor. I checked out the AADSTS75011 at the, to see if there were more details about the error I started digging more into the SAML request and did see Password,ProtectedTransport like the error above. ![]() Related to the failed login screen below, most logins were successful and looking into the user getting failure, the problem could first seem like it was related to pilot users (including myself of course □ ) with passwordless, since the application had not been changed the last 13 months. The users got Azure AD prompt, with the error below:ĪADSTS75011 authentication method ‘x509′, Multifactor’ by which the user authenticated with the service doesn’t match requested authentication method ‘Password, ProtectedTransport’. I had some trouble with an Azure AD integration with a 3.party SAML application.
0 Comments
Leave a Reply. |