OIDC with Entra
OpenID Connect OIDC is an identity protocol built on top of OAuth 2.0 that enables secure authentication and authorization for web and mobile applications. It allows users to log in securely to various services while enabling service providers to access verified identity information.
This guide describes how to configure OpenID Connect in Relution using Microsoft Azure as the identity provider.
<Provider name> Users and creates this group in the organization if necessary. This group can be used to assign permissions.Settings in Relution
OIDC can be configured in the Relution portal under Settings → User Management → OpenID Connect.
The following screenshots include a working configuration example with Microsoft Azure.

Configuration details
Provider name: Required. Displayed as the label on the login button in the Relution portal. It cannot be changed after saving. Create unknown users in Relution: Relution creates new users automatically upon successful login with valid OIDC credentials. The switch is disabled by default. In that case, only users who already exist in Relution can log in. Check configuration: Checks whether the configuration is valid before it is saved.
If a login is done with an unknown user on the store organization with OIDC configured, it will be created in the store organization. In the case of multiple clients with OIDC configuration, the login must be made via the organization URL so that the unknown user is created in the corresponding organization. This URL is displayed in the portal in the OIDC connections.
Client Details
Client ID: Corresponds to the application ID in Azure. Client Secret: Corresponds to the client secret of the application ID in Azure. When a saved configuration is edited, the field stays empty. If no new value is entered, the existing secret remains unchanged; as of Relution 27.0.1, however, only as long as Issuer URI, Authorization URI, Token URI, JWK Set URI and User Info URI are unchanged.
If one of these endpoints was changed and Client Secret is left empty, Relution rejects the save. Client Secret becomes a required field, the placeholder and the hint “Leave the client secret blank to leave the secret unchanged” disappear, and the message “The connection endpoint has changed. Please enter the password or secret again.” appears below the field. After the secret is entered again, the configuration can be saved. Switching between Use discovery endpoint and Manually configure endpoints also counts as a change. Differences in notation only (leading or trailing spaces, a trailing slash, upper or lower case in scheme and host) do not count, nor do changes to End session endpoint, Client ID, Scope or other fields. If no secret has been saved yet, this check does not apply. Via the REST API, the server responds in this case with HTTP 422 and error code 3418.
Server URIs
Use discovery endpoint: If supported by the provider, an automatic configuration of the required URIs is performed. Manually configure endpoints: Necessary as soon as automatic discovery does not work.
If using Microsoft Azure, endpoints must be entered manually.

Authorization URI:
https://login.microsoftonline.com/$-your-tenant-ID/oauth2/v2.0/authorizeJWK Set URI:
https://login.microsoftonline.com/common/discovery/keysToken URI:
https://login.microsoftonline.com/$-your-tenant-ID/oauth2/v2.0/tokenEnd session endpoint (optional, for signing out at the IdP, see Logout verification):
https://login.microsoftonline.com/$-your-tenant-ID/oauth2/v2.0/logout
Extended configuration
Username attribute from OIDC Provider: Specifies the attribute that contains the unique user ID from the identity provider (default: email).
Username attribute from Relution: Defines which Relution user property (User name, E-mail address, UUID or Foreign key (UID); default: E-mail address) is matched against the value of the username attribute from the OIDC provider. With UUID, unknown users are not created even if Create unknown users in Relution is enabled.
Authorization Grant Type: The Authorization Grant Type is an OAuth mechanism that specifies how an application obtains access permissions from a user (default: authorization_code).
Scope: Specifies the identity information or resources the application can request from the OIDC provider (default: openid, email, profile).
Advanced Options
Logout user from OIDC when logging out from Relution: When logging out of Relution, the browser is additionally redirected to the logout endpoint of the IdP (default: disabled). Details are described under Logout verification.
Creating a new app registration
- After signing in to the Azure portal, Microsoft Entra ID is opened.

- A new registration for OIDC is created via
App registrations→New registration.
- A name is entered, the account type Only accounts in this organization directory is selected and the app is registered.

Signing in via OIDC alone requires no additional API permissions and no admin consent. The application permissions for Microsoft Graph (e.g. User.Read.All) are only needed for linking Microsoft Entra ID → and are configured there.
Adding a client secret under Certificates & secrets
- The required client secret is created under Add a certificate or secret.

- Via New client secret, the Description and expiration Expires can be set.

- The client secret can be copied directly.

Add redirection URI
New in 26.4The redirection URI will be displayed in the Relution portal once the connection is configured and saved.


Migration notice — Scoped redirect URIs (from 26.4.0). With 26.4.0 Relution changed the redirect URI scheme: login callbacks are now scoped so they can in future be gated per path on a reverse proxy. The redirect URIs that must be registered depend on the respective OIDC configuration: configurations created from 26.4 onward always use the scoped redirect URIs. Configurations created before 26.4 keep using the previous redirect URI (/login/oauth2/code/) until they are switched to scoped paths (see Switching existing configurations).
From 26.5.0, logins during a device enrollment (enrollment), in the Relution Agent (agent), in Relution Assets (assets) and in the Self-Service Portal (selfService) additionally run through dedicated scopes. If the configuration uses scoped paths and these logins are used with OIDC, the corresponding URIs must be registered at the identity provider.
Where to find them: the redirect URIs for the instance are shown in the Relution portal under Settings → User Management → OpenID Connect in the configuration’s Scoped OIDC URLs section once the connection is saved, and they can be copied from there. However, the portal only shows the entries Redirect URL (management), Redirect URL (device) and, with an Education license, Redirect URL (teacher). It currently does not show the URIs for device enrollment (/api/enrollment/), the Relution Agent (/api/agent/), Relution Assets (/api/assets/), the Self-Service Portal (/api/selfService/) and Relution as Identity Provider → (/api/idp/). These are added manually following the scheme below, as far as the respective function is used with OIDC.
Previous paths (configurations created before 26.4, one redirect URI):
https://<host>/login/oauth2/code/<registrationId>
Scoped paths (configurations created from 26.4 or switched, register all that apply):
https://<host>/api/management/login/oauth2/code/<registrationId> # Relution portal
https://<host>/api/enrollment/login/oauth2/code/<registrationId> # device enrollment (ADE, User Enrollment, Android Enterprise), from 26.5
https://<host>/api/teacher/login/oauth2/code/<registrationId> # Education license only
https://<host>/api/agent/login/oauth2/code/<registrationId> # Relution Agent, from 26.5
https://<host>/api/assets/login/oauth2/code/<registrationId> # Relution Assets, from 26.5
https://<host>/api/selfService/login/oauth2/code/<registrationId> # Self-Service Portal, from 26.5
https://<host>/api/idp/login/oauth2/code/<registrationId> # Relution as Identity Provider (beta), from 26.5
https://<host>/api/device/login/oauth2/code/<registrationId> # 26.4.x only, no longer used by any login from 26.5
<registrationId> is the OIDC configuration UUID shown in Relution.
Logout URLs: The portal additionally shows two logout URLs in the same section. They are not redirect URIs:
- Front-channel logout URL:
https://<host>/api/management/v1/logout/connect/front-channel/<registrationId> - Back-channel logout URL:
https://<host>/api/management/logout/connect/back-channel/<registrationId>
Switching existing configurations
Configurations created before 26.4 keep using the previous redirect URI after the update. Such a configuration additionally shows the Legacy OIDC URLs section with the currently active redirect URL and the previous back-channel logout URL. The switch is done in two steps:
- All applicable scoped URIs are added to the existing Entra app registration. The previous URI remains registered for now.
- In Relution, the configuration is opened under
Settings→User Management→OpenID Connect, Enable Scoped OIDC Paths is clicked in the Legacy OIDC URLs section and the following dialog is confirmed.
Newly created configurations do not show this section, because they use the scoped URIs from the start. The previous URI is deprecated and may be removed in a future release.
Redirect URI for device enrollment
New in 26.5From Relution 26.5.0, all logins during an enrollment use a dedicated enrollment scope. This applies to Apple Automated Device Enrollment (ADE, DEP in the portal), Apple Account-Driven User Enrollment, Android Enterprise enrollment and the Android Enterprise DPC sign-in. For configurations with scoped paths, these logins only work if the /api/enrollment/ URI listed above is registered at the identity provider. Configurations with the previous paths keep using the previous URI for enrollments as well.
Symptom of a missing URI: logging in to the Relution portal keeps working, because it uses the /api/management/ URI. Only the device enrollment fails, for example the ADE enrollment of a Mac with the message AADSTS50011: The redirect URI ... does not match. If this error occurs during an enrollment with a configuration that uses scoped paths, the /api/enrollment/ URI is missing from the Entra app registration.
Backchannel Logout
Relution supports Backchannel Logout.
Example use case: A user is signed in to a central SSO service and multiple applications. When the user logs out of the SSO service, the backchannel logout ensures that all connected applications also terminate their sessions—even if running in the background.
Entra User Requirements for OIDC

Logout Verification
Before go-live, the logout paths should be verified:
- Signing out at the IdP when logging out of Relution: clicking Logout in Relution revokes the session. The browser is only additionally redirected to the logout endpoint of the IdP if the Logout user from OIDC when logging out from Relution switch is enabled under Advanced Options and an end session endpoint is known. Since the endpoints for Entra are configured manually, the End session endpoint field must be filled in for this.
- Front-channel logout: when the user signs out at the IdP, the IdP calls the Front-channel logout URL shown in the portal and Relution revokes the session. This requires the URL to be registered at the IdP.
- Back-channel logout: the IdP sends a logout notification to the Back-channel logout URL — the session is revoked without user interaction.
Testing these paths ensures that IdP-initiated session termination (e.g. from the IdP admin console) propagates correctly to Relution.