Google and Microsoft authenticator entries unreliable when using custom MFA classic login

Help
,
1

Hi There,

We are using custom MFA screens and providing user option to use MFA app (Auth0 Guardian, Google-Authenticator and Mircosoft-Authenticator).
In MFA app, we want the content to be displayed as

Prisidio
useremail@x.com

When initializing guardian, we are providing name and label as below:

                issuer: {
                  name: "{{ userData.email }}",
                  label: "Prisidio",
                }

which gives us the closest behaviour we want.
In Auth0 Guardian app, we see

Prisidio
useremail@x.com

In Google Authenticator, we see

useremail@x.com (useremail@x.com)

In Microsoft authenticator, we see

prisid
useremail@x.com

I attached the screenshots for above examples.
How can we ensure Google and Microsoft Authenticator also shows content similar to what we see in Guardian app?

guardian
guardian900×1600 59.6 KB

google
google900×1600 41.5 KB

microsoft
microsoft900×1600 49 KB

2

IOS app for guardian Auth0 doesn’t behave the same as Android app.
IOS app doesn’t display email like android app.
This is such a bad issue, the functionality changes across platforms.

IMG_9A1F2BE99B3C-1
IMG_9A1F2BE99B3C-11170×2532 75.2 KB

3

Support team provided us a fix. accountLabel was the missing part. Below configuration reliably shows what we want.

Prisidio
UserEmail

Below is the piece of code we had to add in custom MFA code provided at auth0-guardian.js/example at master · auth0/auth0-guardian.js · GitHub

                issuer: {
                  name: "Prisidio",
                  label: "Prisidio",
                },
                accountLabel: "{{ userData.email }}",
1 Like
4

Perfect! Thanks for sharing that with the rest of community!