MFA audience with custom domain

Get Help
,
1

I am using a custom domain, but when I try to use the mfa audience https://mycustomdomain.com/mfa/ I get a service not found error.

I am now using the https://{appname}.auth0app.com/mfa/ format and this works. The problem I am having is showing the universal login branding that I had linked to the custom domain, because now the app logs in the user at the new url.

Is there anyway to use the custom branding with this /mfa/ audience?

3

Hi @jpalacios

Thank you for reaching out to us!

I understand that you are looking to use custom branding on the /mfa/ audience and interested if this is possible.

Recommended Solution

Based on the information provided, it is likely that the audience URL that you set might still be the reason for the behaviour that you are seeing. Even though you have setup a Custom Domain on your tenant, when calling API endpoints such as /mfa, the audience specified needs to still be your canonical tenant domain, namely https://{YOUR_TENANT_NAME}.{REGION}.auth0app.com/mfa.

When you made the change to the https://{appname}.auth0app.com/mfa/ URL, this cause the technical handshake to work, but it redirected your user to the default Auth0 domain instead of your custom domain, which resulted in the Universal Login Branding to no longer apply.

Recommended documentations and Knowledge Articles that can further assist on this matter:

Let me know if that worked! Please do not hesitate to reach out to us for any other issues or requests.

Best regards,
Gerald

4

Sorry I should have clarified the URL more. I just didn’t want to post my instance, but yes I am using https://{YOUR_TENANT_NAME}.{REGION}.auth0app.com/mfa . The main difference is that I no longer have the footer when using this audience, and the organization colors are being applied.

5

@gerald.czifra Any update on this?

6

Hi @jpalacios

Thank you for circling back!

Official expected behaviour

The /mfa endpoint represents an Auth0 API which cannot be changed to accommodate branding in cases like this where the canonical domain is a requirement. I understand how this can cause frustration and I would say that at the moment the flow works as intended ( with regards to the specified audience).

Recommended workaround

I recommend submitting a Feature Request where other users can cast their vote and possibly expedite the development of such a feature. The page is monitored by our Product team who have visibility over all submissions.

Hope this helped provide some clarification!

Have a great one,
Gerald