Infos zum Start & Grundlagen
Organisation, Kanäle und Mixes
Funktions-& Leistungsbeschreibung
Datenschutz
Grundlage Datenschutzkonzept(e)
Verwaltung Zugangsdaten der Nutzenden
Personenbezogene Daten und Datenkategorien
Informationssicherheit
Informationssicherheit bei tchop
App Customization & Deployment
Mobile App Deployment & Vertrieb
Analytics & Reporting
Projektsteuerung
Sonstiges
Languages
OpenID Connect (OIDC) is a simple identity layer on top of the OAuth 2.0 protocol. It allows tchop to verify the identity of a user based on the authentication performed by an authorization server and obtain basic profile information about the user in an interoperable and REST-like manner. It uses security tokens containing assertions to pass information about a user between the following:
This section demonstrates how to create an OIDC SSO application integration between Azure Active Directory and your tchop environment. Steps in this section take place on the Azure Active Directory platform. These instructions are for example purposes only and may not reflect the current Azure Active Directory or your identity provider UI. Refer to the your identity provider documentation for instructions.
<aside> ➡️ You must have an active Azure Active Directory account populated with user names.
</aside>
To configure the integration for tchop:
Log into your account and click on the Microsoft Entra ID icon.

From the left-side menu, navigate to the App registrations tab and select "New registration."

Create your new app
On the Register an application page, give the application a name.
Set Supported account types to Accounts in this organizational directory only (Default Directory only - Single tenant).
Click Register.
Copy the Application (client) ID and save for later.

Click Add a Redirect URI.
Under Platform configurations, click Add a platform.
Select Web.
Enter the following Redirect URI:
Sign-in redirect URIs:
For WebApp: Enter https://[ORGANISATION].[DOMAIN] /webapp/auth/login.
For example: https://meganews.tchop.io/webapp/auth/login
For Mobile Apps:
<android_bundle_id>://login-callback<android_bundle_id>://oidc/login-callback<iOS_bundle_id>://login-callbackSign-out redirect URIs (Only required for Mobile App):
<android_bundle_id>://logout-callback<android_bundle_id>://oidc/logout-callback<iOS_bundle_id>://logout-callback<aside> ➡️ The client needs to add full list of redirect urls for webApp for all channels:
[ORGANISATION].[DOMAIN] /webapp/auth/login[CHANNEL1-ORGANISATION].[DOMAIN] /webapp/auth/login[CHANNEL2-ORGANISATION].[DOMAIN] /webapp/auth/login[CHANNEL3-ORGANISATION].[DOMAIN] /webapp/auth/login<aside> ⚠️ Please check: Some OIDC providers support wildcard on the redirect url eg https://.tchop.it/webapp/auth/login, so we don’t need hardcode all possible combination of subdomains. Just add “https://.tchop.it/webapp/auth/login” to the redirect URL
</aside>
</aside>
Click Configure.
Under Manage, select Certificates & secrets.
Click New client secret.
Give the secret a name and set the expiration date to your company's policy (Keep in mind that when this client secret expires, you need to manually update the new value in tchop, we need to renew the client secret or else SSO will not work)

Copy the Value.

.
<aside> ➡️ The proper format of the Issuer URL is https://login.microsoftonline.com/{tenant_id}/v2.0. You will find the tenant_id in Azure AD (Microsoft Entra ID) → Default Directory → Overview.
</aside>
Now, you are ready to create an OIDC service provider on the tchop server. Refer to the section “Creating an OIDC service provider” for details.
This section demonstrates how to create an OIDC SSO application integration between OKTA and your tchop environment. Steps in this section take place on the Okta platform. These instructions are for example purposes only and may not reflect the current Okta or your identity provider UI. Refer to the your identity provider documentation for instructions.
<aside> ➡️ You must have an active Okta account populated with user names.
</aside>
To configure the integration for tchop: