Infos zum Start & Grundlagen

Einleitung

Organisation, Kanäle und Mixes

Posts, Karten & Content Typen

Rollen für Nutzende

Community Funktionen

Mobile Apps & Web App

Funktions-& Leistungsbeschreibung

Tech Stack

Support

Datenschutz

Grundlage Datenschutzkonzept(e)

Nutzungsauswertung

Verwaltung Zugangsdaten der Nutzenden

Personenbezogene Daten und Datenkategorien

Inhalte in App und Web

Auftragsdatenverarbeiter

TOMs

Informationssicherheit

Informationssicherheit bei tchop

Sicherheitsrichtlinie

ISO27001 Zertifikat

Sicherer Zugang

Schwachstellenanalyse

Risikoanalyse

Kommunikationsmatrix

App Customization & Deployment

Bereitstellung Apps

Mobile App Deployment & Vertrieb

App Customization

App Updates

SSO via SAML

SSO via Open ID Connect

Analytics & Reporting

Grundlagen KPIs

Analytics Dashboard

Projektsteuerung

Arbeitspakete & Timeline

Enablement

Launch & Onboarding

Betriebsrat

Beispiele & Vorlagen

Sonstiges

Feature Roadmap

Languages

English

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:

Configuring an Azure Active Directory integration (Now Microsoft Entra ID) (Example)

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:

  1. Log into your account and click on the Microsoft Entra ID icon.

    Untitled

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

    Untitled

  3. Create your new app

  4. On the Register an application page, give the application a name.

  5. Set Supported account types to Accounts in this organizational directory only (Default Directory only - Single tenant).

  6. Click Register.

  7. Copy the Application (client) ID and save for later.

    Untitled

  8. Click Add a Redirect URI.

  9. Under Platform configurations, click Add a platform.

  10. Select Web.

  11. Enter the following Redirect URI:

    <aside> ➡️ The client needs to add full list of redirect urls for webApp for all channels:

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

    1. Click Configure.

    2. Under Manage, select Certificates & secrets.

    3. Click New client secret.

    4. 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)

      Untitled

    5. Copy the Value.

      Untitled

    .

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

Configuring an OKTA integration (Example)

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:

  1. Sign in to the Okta account and navigate to the Applications dashboard.