Authentication method by which the user authenticated with the service doesn't match requested authe

[Moses E Ali]

Hi,

Is there anything we can do about this within SNOW; As devices on the “new” tenant are cloud joined, our options within Azure are limited as Msft handles Windows Hello for Business. For the old tenant, devices were Hybrid joined and local AD managed Windows Hello for Business.

Basically, what happens is, if the user signs in with their “password”, they can log into SNOW PROD “automatically” with SSO. If they sign into their laptop using Biometrics (PIN or fingerprint), it will fail. They get the error below.

For DEV and TEST, as “Auto-redirect Idp” is disabled for the Identity Provider, SSO will work when entering their email address manually (external login) when using Biometrics to sign into Windows.

We are currently migrating users devices to the new tenant post Domain migration and the current workaround is to use an Incognito browser session or log into Windows with password which is not ideal for the user.

Error - AADSTS75011 Authentication method by which the user authenticated with the service doesn't m...

[Randheer Singh · Accepted solution]

Hi @Moses E Ali ,
Could you please elaborate more about the issue you are facing? When Auto-redirect IdP is not set users need to provide an identifier like email/User Id. Based on the identifier users get redirected to IdP that is associated with their own user record/company record.

if we want users to get redirected to a particular IdP by setting auto-redirect IdP, you can create a URL with a pattern like this "/login_with_sso.do?glide_sso_id=<sys_id_of_your_idp>".

[Moses E Ali]

Randheer, thank you for the answer. It appears it was more of a issue with auto-redirect URL.