Aller au contenu principal
Version 0.1Brouillon

Consent simulator

Overview​

The Consent Simulator renders your application's consent dialogue exactly as LuxID would show it to a user, using your registered name, logo, description, requested scopes, and per-language claim labels.

Before real users see your application's consent screen, you should review exactly what it looks like - across every language LuxID supports, for every combination of scopes your application requests.

The Consent Simulator renders the consent dialogue as LuxID would show it to a user, using your application's actual configuration: registered name, logo, description, requested scopes, and the human-readable claim labels associated with each scope.

The Consent Simulator is accessible via: LuxID Console > Your Application > Preview > Consent Screen

The consent screen is the moment at which a user decides whether to trust your application with their data. A poorly configured consent screen can:

  • Show technical claim names (phone_number, luxid_verified) instead of human-readable labels - confusing users and reducing conversion.
  • Display the wrong application name or a missing logo - undermining trust.
  • Show an English-only description to a Luxembourgish or French-speaking user - reducing comprehension and consent rates.
  • Request claims the user was not expecting - triggering abandonment or support contacts.

The Consent Simulator catches all of these before a real user encounters them.

Step 1 - open the simulator​

In the LuxID Console, navigate to your UAT application. Select Preview from the top navigation, then Consent Screen.

Step 2 - choose an Application​

If you have multiple applications registered (for example, separate applications for web and mobile), select the one you want to preview from the application dropdown.

The simulator always uses the currently saved configuration for that application. If you have unsaved changes in the Console, save them first.

Step 3 - choose a test user​

Select a test user from your UAT user pool. The simulator uses the selected user's actual attribute values to populate the consent screen - this matters because some claims are conditionally shown only when the user actually holds that attribute.

For example:

  • If you request phone_number but the selected test user has no phone number registered, the screen will show the claim as "not available for this user" (or omit it, depending on your configuration).
  • If you request luxid_verified and the test user has completed LuxID Verified identity verification, the claim will appear with a verified badge.

Use the Test users and simulation panel to create test users that cover the attribute combinations you need to preview.

Step 4 - choose a target language​

LuxID's consent screen is available in English, French, German, and Luxembourgish. Select the target language from the language picker:

CodeLanguage
enEnglish
frFrench
deGerman
lbLuxembourgish

The simulator renders the full consent screen in the selected language, including:

  • LuxID's own UI copy (buttons, headings, introductory text).
  • Your application's name and description - in the language you registered it in. If you only provided an English description, that English text will appear in all language variants. See Localising your application metadata below.
  • Claim labels - drawn from the LuxID i18n label set for each supported language.

Step 5 - review the rendered screen​

The simulator displays the consent screen as it would appear in the user's browser. Review the following:

Application identity:

  • Your application's logo appears correctly and is legible at the displayed size.
  • Your application's name is correct and consistent with your branding.
  • Your application's description accurately explains why it needs the listed permissions, in the user's language.

Claim labels:

  • Each requested claim appears with a human-readable label, not a technical field name.
  • The label is meaningful in the displayed language.
  • If a claim label shows a raw technical name (for example, phone_number instead of "Phone number"), you have a label configuration gap - see Fixing missing claim labels below.

Claim grouping:

  • Claims are grouped logically (for example, basic profile information together, contact details together, identity verification separately).
  • The grouping makes sense to a non-technical user.

Optional vs required claims:

  • Claims the user can decline individually are shown with a toggle.
  • Required claims (those your application cannot function without) are shown as mandatory.

Screenshot​

The Consent Simulator rendering a consent screen in French for a test user with verified identity.

Localising your Application metadata​

Your application's name and description are registered with LuxID. LuxID supports per-language versions of both fields. If you serve users in multiple languages, you should register translations for each supported language.

To add translations:

  1. Open your application with LuxID.
  2. Navigate to Application settings > Branding.
  3. For each supported language (en, fr, de, lb), enter the localised name and description.
  4. Save and re-open the Consent Simulator to verify each language variant.

If no translation is provided for a language, LuxID falls back to the English version. This is acceptable for early development but should be resolved before going live with non-English user audiences.

Fixing missing claim labels​

If the consent screen shows a technical field name instead of a human-readable label, the cause is almost always one of the following:

The claim label is not configured in the LuxID i18n label set​

LuxID maintains a set of human-readable labels for every standard claim and for LuxID-specific claims (luxid_verified, luxid_assurance_level, etc.). If your application uses a custom claim that falls outside the standard set, contact LuxID to request a label be added to the i18n set, or discuss an alternative approach.

You are requesting a claim that LuxID does not recognise​

If the field name shown on the consent screen is not a standard OIDC claim and not a documented LuxID extension claim, you may be requesting a scope that does not map to a supported claim. Review your scope parameter against the LuxID supported scope list in the OpenID Connect reference.

The Claim Template is missing​

Claim Templates control which claims are released for a given application. If a claim is not in your Claim Template, it will not appear on the consent screen - or it may appear with a fallback label. Verify your Claim Template configuration with LuxID under Application settings > Claims.

Validating branding assets​

The Consent Simulator is also the correct place to verify your logo. LuxID applies specific sizing and background treatment to application logos on the consent screen. Use the simulator to confirm:

  • The logo is legible at the displayed size (typically 64x64 or 128x128 pixels).
  • The logo has an appropriate background (transparent or white) and is not lost against the consent screen's background colour.
  • The logo is the correct variant (colour logo on a light background).

For logo format requirements, see the UX and Branding section (cross-reference available when that section is published).

Use cases by role​

Developer:

  • Confirm that all scopes in the authorisation request produce the expected consent items.
  • Confirm that no unexpected or redundant claims appear (for example, requesting profile when only name is needed).
  • Verify that optional and required claim toggles are configured correctly.

QA engineer:

  • Run through all four language variants before each release.
  • Include consent screen screenshots in release sign-off artefacts.
  • Verify behaviour for test users with different attribute profiles (verified vs unverified, with vs without phone number).

Product owner / UX designer:

  • Review the application description and name in each language.
  • Confirm the overall consent screen layout and copy meets brand and legal requirements.
  • Approve the final consent screen configuration before go-live.

Checklist before go-live​

Use this checklist when reviewing the Consent Simulator output:

  • Application logo is correct and legible.
  • Application name is correct in all four languages (en, fr, de, lb).
  • Application description is clear and translated in all four languages.
  • All requested claims have human-readable labels (no raw field names visible).
  • Claim grouping is logical and non-technical users can understand it.
  • Optional claims have toggles; required claims are marked as mandatory.
  • Consent screen has been reviewed in all four language variants.
  • A test user with LuxID Verified status has been used to check identity verification claim presentation (if applicable).
  • A test user without a phone number has been used to check phone_number conditional display (if applicable).
Mise à jour le 2026-05-22
Sur cette page