CODEWITHSUNDEEP
azure-active-directorytwo-factor-authenticationmulti-factor-authentication
appalling22
appalling22

Reputation: 117

AzureAD custom multi factor auth

I've got a single page application that currently uses Azure AD B2C authentication to allow users to sign in, and then use the auth cookies to talk directly to internal services. There is now a requirement that we use two factor auth on top of the existing AD auth. We've already rolled our own 'second factor' auth, and we need to be able to integrate with that (I'd much rather use the built in MFA that Azure provides, but for this question assume that isn't an option).

Our issue is that we don't want to call our MFA service until the user has authenticated succesfully with AD - but of course, once they have, they are already authenticated, and it's too late.

When Azure AD hands back to us via the call back (we are using CookieAuthenticationEvents), is there any way to defer the access token being available until our own second factor auth step succeeds?

Upvotes: 1

Views: 163

Answers (1)

Tony Ju
Tony Ju

Reputation: 15619

Just as juunas suggested, try to use custom polices which are designed primarily to address complex scenarios.

Reference:

Custom policies in Azure Active Directory B2C

Upvotes: 1

Related Questions