--- title: "Set up OpenID Connect login for the Merchant Backend" slug: "set-up-openid-connect-login-for-the-merchant-backend" description: "Streamline Merchant Backend logins with OpenID Connect, allowing users to access with their identity provider credentials for enhanced security and convenience." updated: 2026-08-17T13:50:27Z published: 2026-08-17T13:50:27Z canonical: "help.frisbii.com/set-up-openid-connect-login-for-the-merchant-backend" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.frisbii.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up OpenID Connect login for the Merchant Backend ## Overview OpenID Connect (OIDC) lets your Merchant Backend users log in with the credentials from your company's own identity provider — for example Microsoft Entra ID — instead of a separate Frisbii Media password. An administrator connects the identity provider once at contracting company level, and users can then sign in to the Merchant Backend with a single click. --- ## Before you begin - You have the **Administrator** role in the Merchant Backend for the contracting company. - Your company uses an identity provider that supports OpenID Connect, for example Microsoft Entra ID. - You can create or configure an application registration with your identity provider, or someone in your IT team can do this for you. - You have decided which user group newly created users should be added to by default. See [Create user groups](/frisbii-media/docs/benutzergruppen-anlegen). --- ## Connect your identity provider 1. Open the contracting company's Merchant Backend and navigate to **Settings → User Administration → Backend Security Settings**. 2. In the **Authentication Provider** section, click **Edit**. 3. Enter the connection details: You get these information from your authentication provider platform (e.g. [Microsoft Entra ID](https://learn.microsoft.com/de-de/azure/app-service/configure-authentication-provider-aad?tabs=workforce-configuration), [Okta](https://developer.okta.com/docs/guides/find-your-app-credentials/main/), [AuthO](https://auth0.com/docs/get-started/applications/application-settings), etc.). 4. Choose the user group that new Merchant Backend users are automatically added to the first time they log in via OpenID Connect. You can change the user's user group anytime after initial login (User Administration → Users). 5. Choose to force OpenID connect login for all users. > **Note** > > You can keep password login available alongside OpenID Connect, or require OpenID Connect for all accounts with the User role. Administrator accounts always fall back to password login, even when OpenID Connect is required for everyone else. 6. Enter your email domain(s) with which users should be able to log in. > [!CAUTION] > Limitations > > Public email domains cannot be used for SSO. Please use a domain your company owns. The following domains are not supported: `gmail.com` , `googlemail.com` , `outlook.com` , `hotmail.com` , `live.com` , `yahoo.com` , `icloud.com` , `aol.com` , `gmx.de` , `gmx.net` , `web.de` , `t-online.de` , `freenet.de` , `email.com` , `proton.me` 7. Click on **Save**. ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-62QQOG7K.png) When the connection is complete, the Authentication Provider section shows your connected identity provider, and the **Login with SSO** option becomes available on the Merchant Backend login page. --- ## How user accounts are created and matched - If a Merchant Backend account already exists with the same email address, that account is used for the login — no duplicate account is created. - If no matching account exists, a new user is created automatically on first login, with the **User** role and the default user group you selected. - Once a user logs in via OpenID Connect, they can no longer use password login or reset their password directly if "Force OpenID Connect login" is activated. An administrator can switch a user back to password login at any time from **User Administration → Users**. --- ## How your users log in 1. On the Merchant Backend login page, the user enters their email address and selects **Log in with SSO**. 2. **Sign in with your identity provider** — Selecting **Login with SSO** redirects the user to your identity provider to sign in. Once the identity provider confirms the login, the user is redirected back and signed in to the Merchant Backend. ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-9ELTW73X.png) --- ## Related - [Create user groups](/benutzergruppen-anlegen.md) - [Create user](/benutzer-anlegen.md)