# app\_metadata / user\_metadata not delivered to custom ACUL MFA screens despite context\_configuration

**URL:** <https://community.auth0.com/t/app-metadata-user-metadata-not-delivered-to-custom-acul-mfa-screens-despite-context-configuration/202227>\
**Category:** Get Help\
**Tags:** login-experience\
**Created:** [August 3, 2026, 1:27pm UTC](https://community.auth0.com/t/app-metadata-user-metadata-not-delivered-to-custom-acul-mfa-screens-despite-context-configuration/202227 "2026-08-03T13:27:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![besabeteng](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/besabeteng/32/60160_2.png) [@besabeteng](https://community.auth0.com/u/besabeteng)\
**Post date:** [August 3, 2026, 1:27pm UTC](https://community.auth0.com/t/app-metadata-user-metadata-not-delivered-to-custom-acul-mfa-screens-despite-context-configuration/202227/1 "2026-08-03T13:27:17Z")

</div>

**Background**  
We use ACUL for our custom Universal Login screens. On the `mfa-webauthn-platform-enrollment` screen we need a per-user flag to drive UI logic, so we added it to the screen’s `context_configuration`

**Problem**  
The values never reach the screen. We verified all three preconditions via the Management API:

- Screen rendering `context_configuration` includes `user.app_metadata.<key>` (and separately `user.user_metadata.<key>`) — confirmed with a `GET` on the screen’s `/rendering`.
- The value is actually set on the user — confirmed with `GET /api/v2/users/{id}` (both `app_metadata` and `user_metadata` contain the key).
- The SDK maps correctly (`user.appMetadata = data?.app_metadata ?? null`).

Yet `window.universal_login_context.user` on the screen contains only `id`, `email`, `picture` — **no `app_metadata` or `user_metadata` at all** , on a fresh login well past any config-propagation window.

**Question**  
Is per-user metadata intentionally withheld on MFA screens (e.g. because the user isn’t fully authenticated mid-MFA)? If so, is that documented, and is there a supported way to pass a per-transaction/per-user value into a custom MFA screen? We’ve confirmed there’s no Action→ACUL data channel, and `enrolled_factors` isn’t an available context field either.

Environment: ACUL `@auth0/auth0-acul-js` v1.5.0, New Universal Login, advanced rendering mode.

* * *

---

<div class="post-metadata">

**Author:** ![remus.ivan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/remus.ivan/32/68771_2.png) [@remus.ivan](https://community.auth0.com/u/remus.ivan)\
**Post date:** [August 3, 2026, 7:00pm UTC](https://community.auth0.com/t/app-metadata-user-metadata-not-delivered-to-custom-acul-mfa-screens-despite-context-configuration/202227/3 "2026-08-03T19:00:46Z")

</div>

Hi @besabeteng,

Welcome to the Auth0 Community!

> [@besabeteng](#):
>
> Is per-user metadata intentionally withheld on MFA screens (e.g. because the user isn’t fully authenticated mid-MFA)? If so, is that documented, and is there a supported way to pass a per-transaction/per-user value into a custom MFA screen?

To directly address your questions, user-specific metadata( **`app_metadata` and `user_metadata`** ) is intentionally withheld during MFA and password-reset screens. Because the user is in a “pre-authenticated” or “mid-authenticated” state, Auth0’s security model strictly restricts access to sensitive user metadata properties in the Advanced Customizations for Universal Login (ACUL) runtime context to prevent exposing data before identity is fully verified.

So in order to pass user specific information into ACUL’s MFA screens, I can think of an alternative of working around this by using the `ext-` Query Parameter Strategy.

If the UI logic you are trying to drive is determined at the beginning of the transaction (for example, when your application initiates the login request), you can pass a custom query parameter through the `/authorize` endpoint by following these steps:

1. **Pass the Parameter** : Append your custom parameter with an `ext-` prefix to your authorization URL:

2. **Add to Context Configuration** : In your Management API payload or Terraform configuration for the `mfa-webauthn-platform-enrollment` screen, map this parameter inside the `context_configuration`

3. **Consume in ACUL** : On your custom screen, read the parameter from the untrusted data object

Otherwise, if the UI logic is tied to the client application rather than the individual user you can still take advantage of the `client.metadata.YOUR_KEY` for setting metadata or `organization.metadata.YOUR_KEY`\*\* in the organization metadata context as presented in our [ACUL Rendering Configuration Reference - Dynamic URL segments](https://auth0.com/docs/customize/login-pages/advanced-customizations/configure/reference) to support multi-branding in different ACUL screens, including MFA ones.

Thank you and if you have any other questions please let me know!  
Kind regards,  
Remus

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 5, 2026, 7:01pm UTC](https://community.auth0.com/t/app-metadata-user-metadata-not-delivered-to-custom-acul-mfa-screens-despite-context-configuration/202227/4 "2026-08-05T19:01:38Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
