OIDC with Workspace

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 service providers can simultaneously access verified identity information.

This guide explains the step-by-step configuration of OIDC in Relution using Google Workspace as an example.

When using OIDC, no classes or groups are synchronized. Users are only created in Relution on their first successful login, and only if the Create unknown users in Relution switch is enabled in the OIDC configuration. If it is disabled (default), only users who already exist in Relution can log in. Relution automatically adds newly created users to the group <Provider name> Users, which can be used to assign permissions.

Project and Client Setup (Google Cloud Console)

First, an application must be registered in the Google Cloud Console to obtain the necessary credentials.

  1. The sign-in takes place at console.cloud.google.com →.

  2. A new project is created or an existing one is selected.

    Google Cloud Console project selector showing existing projects and new project option

    Google Cloud Console showing newly created project selected for OIDC configuration

  3. In the navigation menu, APIs & Services → OAuth consent screen is opened and configured if necessary.

    Google Cloud Console APIs and Services OAuth consent screen configuration page

  4. Under Credentials, Create Credentials is clicked and OAuth client ID is selected.

    Google Cloud Console Credentials page with Create Credentials button and OAuth client ID option

  5. For Application type, Web application is selected.

    Google Cloud Console OAuth client type selection with Web application chosen

  6. Under Authorized JavaScript origins, the server URL is entered (e.g., https://support.relution.io). Note: The Authorized redirect URIs field can be left open for now; it will be updated later with the redirect URIs from Relution.

    Google OAuth client configuration with authorized JavaScript origin and redirect URI field

  7. The Client ID displayed after saving is copied.

    Google OAuth client confirmation screen displaying Client ID to copy for Relution

  8. The newly created client is edited again to view the details.

    Google Cloud Console OAuth client details page showing edit option to view credentials

  9. The Client Secret is copied. Both the ID and Secret are kept secure for later use in Relution.

    Google OAuth client secret value displayed for copying to Relution OIDC configuration


SSO Setup (Google Admin Console)

In parallel, the Single Sign-On (SSO) profile must be stored in the Google Admin Console.

  1. admin.google.com → is opened.

  2. A new OIDC profile is created under Security → Authentication → SSO with third-party IdP.

    Google Admin Console Security Authentication SSO with third-party IdP OIDC profile creation

  3. The Client ID and Client Secret obtained in the previous steps are entered.

    • For the Issuer URL and Change password URL, the Relution server URL is used (e.g., https://support.relution.io).
      Google Admin Console OIDC profile form with Client ID, Client Secret and Issuer URL fields

OIDC Configuration in Relution

Now, the collected data is entered into Relution to establish the connection with Google.

  1. The OIDC settings are opened in Relution under Settings → User Management → OpenID Connect.

    Relution Settings OpenID Connect configuration page showing Client ID and Secret fields

  2. Under Provider name, a unique name is entered (e.g. “Google Workspace”). The name appears on the login button and cannot be changed after saving.

  3. If required, Create unknown users in Relution is enabled so that new users are created automatically on their first login.

  4. The Client ID and Client Secret from the Google Cloud Console are entered in the Client ID and Client Secret fields.

  5. In the Server URIs section, Use discovery endpoint is selected and https://accounts.google.com is entered in the Issuer URI field.

  6. The configuration is saved and then opened again to see the generated fields.

  7. In the Scoped OIDC URLs section, all Redirect URL entries shown are copied (one each for management and device, plus teacher with an Education license).

    Relution OIDC configuration showing generated Redirect URL to copy for Google OAuth client

  8. console.cloud.google.com → is opened again.

  9. The OAuth client is edited and all URLs just copied from Relution are added under Authorized redirect URIs. In addition, the redirect URIs that the portal does not display are added, at least the one for device enrollment (/api/enrollment/), see Scoped redirect URIs.

    Google OAuth client authorized redirect URIs field with Relution redirect URL entered

Extended configuration defines how Relution assigns the signed-in user: the Username attribute from OIDC Provider (default: email) is matched against the user property selected under Username attribute from Relution (User name, E-mail address, UUID or Foreign key (UID); default: E-mail address). With UUID, unknown users are not created. The Scope defaults to openid, email, profile. Check configuration validates the configuration before saving.

Scoped redirect URIs

New in 26.4

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. Which redirect URIs are used depends on whether the OIDC configuration still uses the previous paths: 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:

  1. All applicable scoped URIs are added to the existing Google OAuth client. The previous URI remains registered for now.
  2. 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.
The switch cannot be undone. Afterwards, Relution only uses the scoped URIs for this configuration. If one of them is missing at the identity provider, the affected logins fail.

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.5

From 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, with an error about an invalid redirect URI (invalid_redirect_uri, at Google Error 400: redirect_uri_mismatch). If this error occurs during an enrollment with a configuration that uses scoped paths, the /api/enrollment/ URI is missing from the Google OAuth client.


Backchannel Logout

Relution supports Backchannel Logout starting with server version 5.32.0.

Example Scenario: A user is simultaneously logged into multiple applications via SSO. When logging out of the central SSO service, Backchannel Logout ensures that the sessions in Relution and other connected applications are also terminated securely in the background.


Logout Verification

Before go-live, the logout paths should be verified:

  • Signing out at the IdP when logging out of Relution: clicking Logout revokes the session in Relution. If the Logout user from OIDC when logging out from Relution switch is enabled under Advanced Options (default: off) and an end session endpoint is known (entered manually in the End session endpoint field or reported by the IdP via discovery), the browser is additionally redirected to the logout endpoint of the IdP.
  • 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.

How helpful was this article?