Quick integrations (no-code / SaaS)
Who this section is for
This section is for IT administrators and IT teams who need to add LuxID login to an off-the-shelf tool or SaaS platform. No programming is required. You configure settings screens inside your tool of choice - LuxID handles the rest.
If you are building a custom application, this is not your section. See the Authenticate section for code-level integration guides.
The no-code promise
Every guide in this section follows the same pattern:
- Register your application with LuxID (see Configure LuxID)
- Enter your LuxID credentials and endpoints into the tool's SSO settings
- Map claims to local user fields
- Test with a sandbox account
- Switch to production
Most integrations take 10 to 30 minutes. There is no SDK to install, no code to write, and no deployment pipeline to run.
Supported protocols
LuxID speaks two standard identity protocols that nearly every enterprise tool supports:
- OpenID Connect (OIDC) - the default for modern web applications, SaaS, and API-driven tools. Uses a discovery URL to auto-configure most fields
- SAML 2.0 - the standard for legacy enterprise platforms and corporate federation scenarios. Uses metadata XML to configure both sides
If your tool supports both, prefer OIDC. See OIDC vs SAML decision guide for guidance.
Typical scenarios
SME adding customer login to its Odoo e-shop
A small business runs a modest web presence or e-shop on Odoo with a customer login. Rather than make customers create yet another account, it lets them sign in with LuxID. The admin enables Odoo's built-in OIDC SSO module, pastes in the LuxID endpoints, and maps sub, given_name, family_name, and email. No custom development.
Organisation wiring LuxID into WordPress or Drupal
An organisation runs a member or customer portal on WordPress or Drupal. Users log in with LuxID instead of creating a local account. The admin installs a single OIDC contrib module (the daggerhart plugin for WordPress, the openid_connect contrib for Drupal), enters the LuxID OIDC endpoints, Client ID, and Client Secret, and maps the email and name claims to the local user profile. Done.
Enterprise wiring LuxID into Microsoft 365
A Luxembourg enterprise adds LuxID as a federated identity provider in Microsoft Entra External Identities. Employees who do not have an Entra account can sign in to Microsoft 365 apps using their LuxID credentials via SAML federation. The admin exchanges SAML metadata between LuxID and Entra, configures claim mapping, and tests with a guest user.
Do I need this section, or the Authenticate section?
Pages in this section
- Overview - What this section covers, what it does not cover, and the 5-step template
- Before you start - Everything you need to collect before opening a tool's SSO settings
- OIDC vs SAML decision guide - Which protocol to use for your tool
- Tool-specific integrations - Step-by-step guides for Odoo, WordPress, Drupal, ServiceNow, Atlassian, Microsoft 365, Salesforce, and Moodle
- Generic OIDC setup - For any tool that asks for "OpenID Provider details"
- Generic SAML setup - For any tool that asks for "SAML IdP metadata"
- Identity broker integrations - For organisations running their own IdP or federation hub (Keycloak, FusionAuth, Synapse) that want to add LuxID as an upstream identity source