`client.metadata` is not delivered to the reset-password-error screen (ACUL advanced mode), but works on reset-password

Get Help
, , , ,
1

Summary

We use Advanced Customization for Universal Login (ACUL) in advanced rendering mode.
We request the same context_configuration for every screen. client.metadata.* is
delivered on reset-password and reset-password-success, but never on
reset-password-error. On that screen client.id resolves correctly, so the application
is clearly identified, yet the metadata keys are absent from
window.universal_login_context.

Setup

  • Prompt: reset-password. Screens: reset-password, reset-password-success,
    reset-password-error.
  • Rendering mode: advanced
  • SDK: @auth0/auth0-acul-react@1.5.0

What we observe

On reset-password (valid link), window.universal_login_context.client:

{
  "id": "<client id>",
  "name": "<client name>",
  "metadata": { ... }
}

On reset-password-error, reached by clicking an already used reset link:

{
  "id": "<same client id>",
  "name": "<client name>"
}

metadata is absent entirely. Same client, same tenant, same configuration.

What we already ruled out

  1. The configuration is not malformed.
  2. The configuration is stored. We read it back with
    GET /api/v2/prompts/reset-password/screen/reset-password-error/rendering. The
    context_configuration returned is identical to the working reset-password screen.
  3. The client resolves. client.id is present and correct on the error screen, so this is not a case of Auth0 being unable to identify the application.

Questions

  1. Why are the requested client.metadata.* keys not delivered on
    reset-password-error when client.id resolves on the same screen?
  2. Is this an intentional restriction?