LuxID identifiers reference

LuxID surfaces four distinct diagnostic identifiers. They are easy to confuse because several are long hexadecimal strings, but each appears in a different place, is aimed at a different audience, and correlates a different thing. Quoting the wrong one to support wastes a round-trip, so use this page to pick the right identifier for the situation in front of you.

The four identifiers

Identifier	Where it appears	Visible to the end user?	Audience	What it is for	What to ask a user for
Error ID	The authentication error dialog ("Connection error with LuxID") and other known-scenario UI errors. A short symbolic label, e.g. login.	Yes	User and support	Categorises a known failure scenario (for example "user already exists", a login failure). Tells you what kind of error occurred.	Yes - quote it alongside the Transaction ID; it names the scenario.
Transaction ID	The authentication error dialog ("Connection error with LuxID"), shown under the Error ID. A long hexadecimal string (~24 characters), e.g. e0b804c269ef2d7b10cbb7a2.	Yes	User and support	Identifies the specific authentication transaction that failed, so LuxID can locate it in the authentication logs.	Yes - this is the primary correlation handle for a failed sign-in.
Support ID	The WAF (Web Application Firewall) page shown when a request is blocked, or when the backend returns a 500 that the WAF masks.	Yes (on WAF block / masked-500 pages)	User and support	Correlates a request that LuxID's edge blocked or masked, so LuxID can trace it. It is not the general authentication-error correlation ID.	Yes - but only when the user is on a WAF block or "a technical error occurred" masked-500 page, not on the authentication error dialog.
Global Transaction ID	The HTTP response header. Not rendered on any screen.	No	Developers and LuxID	Correlates a request across LuxID's internal logs. Captured from response headers by developer tooling.	No - the user never sees it. Developers can capture it from the response headers and include it in a ticket.

Which one do I ask the user for?

If the user is on the "Connection error with LuxID" authentication dialog, ask for the Error ID and the Transaction ID. If the user is on a WAF block page or a "technical error" masked-500 page, ask for the Support ID. Never ask a user for the Global Transaction ID - it lives only in HTTP headers; a developer captures it, not the user.

How to tell the screens apart

• Authentication error dialog - titled "Connection error with LuxID" (localised per language), names support@luxid.lu, and shows an Error ID plus a long-hex Transaction ID. This is the screen a user reaches when a sign-in transaction fails.
• WAF block / masked-500 page - a generic edge page shown when the request never reached (or was masked at) the LuxID application. It carries a Support ID rather than an Error ID / Transaction ID pair.
• HTTP response - the Global Transaction ID header is present on responses regardless of screen; it is the developer-only tie-breaker when neither on-screen identifier is available.

Related pages

• Diagnose a failing request - decision tree and how to capture the right identifier.
• Logs and audit trails - which identifier the authentication log correlates on.
• Contact and support channels - what to include in a ticket.
• For end users: Fix issues with third-party connections and Error messages and what to do.