Add login to your Application
15-minute quickstart: implement Authorization Code Flow with PKCE against LuxID, with cURL examples, sequence diagram, and ID token validation.
15-minute quickstart: implement Authorization Code Flow with PKCE against LuxID, with cURL examples, sequence diagram, and ID token validation.
Read and revoke the subscription that links a LuxID user to one of your applications.
Discover the LuxID-registered applications and instances that belong to your partnership, and the groups attached to each application.
Step-by-step guide to integrate LuxID with Atlassian Cloud via SAML 2.0: prerequisites, field mapping, testing, and a production checklist.
Roadmap: optional enriched claims beyond standard OIDC profile - organisation, age brackets, residency, postal address - each requiring explicit user consent.
Checklist of prerequisites every IT admin must have in hand before configuring LuxID in an off-the-shelf tool.
Configuring per-Application logos, display names, and localised descriptions shown on the LuxID consent screen, and previewing them before go-live.
How LuxID communicates platform changes to Partners: change categories, notification windows, deprecation policy, communication channels and roadmap visibility.
Set or remove a custom claim value on a subscriber, to be surfaced on subsequent authentications.
Viewing and rotating Client Secrets, and SAML signing certificate lifecycle in the LuxID Console.
Curated index of reference repositories, starter templates, and validation utilities for integrating LuxID with the major language ecosystems.
End-to-end guide: become a LuxID Partner, register an Application, obtain credentials, and complete a first test login using Authorization Code + PKCE.
Patterns for one LuxID application acting on behalf of a user at another service: delegated tokens, token exchange, and refresh token scoping.
A decision tree for diagnosing LuxID integration errors, which on-screen identifier to capture, and what to include when you raise a support ticket.
Step-by-step guide to integrate LuxID with Drupal via OIDC: prerequisites, field mapping, testing, and a production checklist. Typical time: 15-20 min.
How LuxID's Production and UAT environments differ, how to promote an Application between them, and data residency details.
Search the time-ordered stream of user-related events tied to your partnership's applications, with pagination.
Overview of LuxID identity events: the common event envelope, pull vs push delivery, the indicative event catalogue, and SIEM integration.
Add LuxID as an OpenID Connect Identity Provider in FusionAuth, including the reconcile lambda for claim mapping, testing, and production checklist.
Configure any OIDC-capable identity broker against LuxID: discovery URL, PKCE (S256), RS256 ID tokens, exact-match redirect URIs, and JWKS rotation.
Authentication, base URLs, request and response conventions, and the standard error model for the LuxID Partner API.
List partner-managed groups, list members, list a user's group memberships, and add or remove members in bulk.
Configure LuxID as an upstream OIDC provider behind your own broker: Keycloak, FusionAuth, Matrix (Synapse, MAS), SAP Customer Data Cloud, or generic OIDC.
Configuration-level troubleshooting for IT administrators: map what users report to the check to run and the request to raise - no protocol knowledge needed.
Add LuxID as an external OpenID Connect identity provider in Keycloak (Identity Brokering): field mapping, claim mappers, testing, production checklist.
Querying authentication logs, Subscription events, and configuration audit records in the LuxID Console, including filtering, export, and retention.
LuxID acts as an OpenRoaming Wi-Fi identity provider, letting users roam onto participating networks in Luxembourg without re-authentication.
Overview of the LuxID Console - the operational portal for Partner administrators to manage Applications, credentials, logs, and branding.
Server-to-server REST API for LuxID Partners to manage applications, subscriptions, groups, custom claims, and user events programmatically.
LuxID Verified confirms a user's name and date of birth via LuxTrust: verification process, token claims, use cases, and relay-only LoA provenance.
Configure LuxID as an OIDC provider for a Matrix homeserver: legacy Synapse built-in OIDC and the next-gen Matrix Authentication Service (MAS).
Step-by-step guide to integrate LuxID with Microsoft 365 via SAML 2.0: prerequisites, field mapping, testing, and a production checklist.
Step-by-step guide to integrate LuxID with Moodle via OIDC: prerequisites, field mapping, testing, and a production checklist. Typical time: 15-20 min.
LuxID MFA methods (OTP, TOTP, passkeys, LuxTrust), token claims amr and acr, minimum assurance configuration, step-up flows, and recovery paths.
Protecting backend APIs with OAuth 2.0 bearer tokens, scopes, audiences, and machine-to-machine patterns at LuxID.
Step-by-step guide to integrate LuxID with Odoo via OIDC: prerequisites, field mapping, testing, and a production checklist. Typical time: 15-20 min.
Decision matrix and flowchart to help IT admins choose between OpenID Connect and SAML 2.0 when integrating LuxID with an off-the-shelf tool.
What the Quick Integrations section covers, the 5-step template every guide follows, and how to know you are in the right place.
WebAuthn/FIDO2 passkeys on LuxID: device binding, platform and roaming authenticators, token claims, fallback behaviour, and phishing resistance.
Minimal configuration to wire LuxID into Spring, ASP.NET, Node.js, Next.js, React SPA, Angular, React Native, iOS, Android, PHP, and Python.
Security checklist for LuxID integrations: HTTPS, PKCE, state/nonce, ID Token validation, token storage, open redirects, and anti-patterns to avoid.
Rules, configuration steps, and troubleshooting guidance for redirect URIs and domain ownership in LuxID Applications.
What to submit to register a new client Application with LuxID: required fields, claim declarations, access rules, and authentication level configuration.
How to perform every Console operation while self-service is on the roadmap: one request template per operation, all routed via servicedesk@post.lu.
Step-by-step guide to integrate LuxID with Salesforce via OIDC: prerequisites, field mapping, testing, and a production checklist. Typical time: 20-30 min.
Integrating LuxID as a SAML 2.0 Identity Provider: metadata, AuthnRequest, Assertion validation, attribute mapping, and logout behaviour.
How to use the LuxID UAT environment for development and QA: what differs from production, rate limits, test data lifecycle, and promoting to production.
Configure LuxID as an OpenID Connect identity provider in SAP Customer Data Cloud (formerly Gigya): field mapping, JIT account behaviour, and common pitfalls.
End-to-end journey for becoming a LuxID Partner: from first contact through KYB, agreement, UAT integration, go-live review to production credentials.
Step-by-step guide to integrate LuxID with ServiceNow via OIDC or SAML: prerequisites, field mapping, testing, and a production checklist.
How to persist refresh tokens, silently renew sessions, and avoid re-prompting users for credentials and OTP on every app restart.
Consumer SSO across LuxID-enabled apps and LuxID Pro enterprise federation: Sphere boundaries, domain routing, corporate IdP integration, token claims.
Creating and configuring test user accounts in UAT, simulating authentication scenarios, and resetting test user state in the LuxID Console.
Overview of the LuxID developer tools and UAT environment for faster integration development and QA.
Pick your SaaS tool to get a dedicated step-by-step LuxID integration guide: Odoo, WordPress, Drupal, ServiceNow, Atlassian, Microsoft 365, Salesforce, Moodle.
LuxID's hosted login page: redirect-based authentication, branding boundaries, session reuse, and why Partners should never build their own login form.
Subscribe to LuxID identity events via push (webhooks) or pull (Event Hub): subscription management, payload signing, delivery semantics, and replay protection.
Step-by-step guide to integrate LuxID with WordPress via OIDC: prerequisites, field mapping, testing, and a production checklist. Typical time: 15 min.