OpenID Connect Configuration as Identity Provider (OIDC)

August 28, 2025

Contributed by:

This platform supports integration with OpenID Connect for logging in.

Registering the Application

Go to the OpenID Provider’s Developer Portal.
Navigate to the Applications or Clients section.
Click on “Create New Application” or equivalent. Set the following:
App Name: Choose a name that will be displayed to users logging in.
Application Type: Select “Web Application”.
Redirect URIs: Add the following URI to handle login redirects: https://example.com/oauth/callback
Logout Redirect URI: Add the following URI to handle logout redirects: https://example.com/auth/logout
Save the application.

Note the Client ID and Client Secret generated during this process. These will be required for platform configuration.

Configuring Scopes and Claims

Under the Scopes or Permissions section of your application, ensure the following scopes are included:

openid
email
profile
Any additional scopes your platform requires.

Configure claims if necessary. Common claims include:

sub: Unique identifier for the user.
email: User’s email address.
name: Full name of the user.
preferred_username: Username or handle.

Enabling Single Logout (SLO)

To enable Single Logout (SLO) for OpenID Connect:

Navigate to the Advanced Settings or Logout Configuration section.

Enable Single Logout if supported by the provider.

Add the Logout Redirect URI configured earlier:

https://example.com/auth/logout

Optionally, add the following claims to the ID token:

sid: Session identifier.
logout_hint: Provides context for logging out.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

OpenID Connect Configuration as Identity Provider (OIDC)

August 28, 2025

Contributed by:

August 28, 2025

Contributed by:

OpenID Connect Configuration as Identity Provider (OIDC)

Registering the Application

Configuring Scopes and Claims

Enabling Single Logout (SLO)

In this article