search

damienbod / MfaServer

Microsoft Entra ID external authentication methods
https://learn.microsoft.com/en-gb/entra/identity/authentication/concept-authentication-external-method-provider
MIT License
14 stars 3 forks source link

Could not verify assertion #7

Closed bastarz closed 1 month ago

bastarz commented 4 months ago

After the redirect from Entra ID to the MFA Server, I can see, that the information from the token were used to display the username but when I click on the authenticate button, I only get the following error message:

image

any ideas, what the issue could be? It seems, that it´s somehow related to the verifiyAssertionsWithServer(credential) Method, which is defined in the passwordless.login.js file.

bastarz commented 4 months ago

@damienbod I´ve figured out what the issue is. I´m using ngrok as reverse proxy and after updating the appsetings.json configuration "Fido2": { // This must match the deployment domain "ServerName": "FidoMfaServer", "ServerDomain": "de215.ngrok.app", "Origins": [ "https://de215.ngrok.app" ], "TimestampDriftTolerance": 300000, "MDSAccessKey": null }, I thought, that the PwFido2SignInController and PwFido2RegsiterController would apply the settings automatically but it´s not the case. I got e.g. always "localhost" as ServerDomain. After updating the Fido2 configuration in the PwFido2SignInController and PwFido2RegsiterController manually I was able to register my Fido2 key and also use it successfully as authn factor. Do you maybe know, where the ServerDomain and Origins configuration could else be stored?