Google Workspace Setup for Open WebUI

This guide explains how to configure Google Workspace as the Identity Provider (IdP) for Arthur’s Keycloak, which brokers authentication into Open WebUI.

The goal is to let organizations control admin and user access in Open WebUI based on their Google Group memberships — for example:


Before You Begin

You’ll need:

  • Access to your organization’s Google Admin Console (not Google Cloud Console)
  • At least one Google Group created for Open WebUI admins (e.g. [email protected])
  • The Keycloak ACS URL and Entity ID provided by Arthur (see below)

Step 1 — Open the Google Admin Console

  1. Go to https://admin.google.com
  2. Sign in with an account that has Super Admin privileges.

Step 2 — Create a Custom SAML App

  1. In the left sidebar: Apps → Web and mobile apps → Add app → Add custom SAML app
  2. Enter an app name such as “Open WebUI (Arthur)”
  3. (Optional) Upload your company or Arthur logo for easy identification.
  4. Click Continue

Step 3 — Download Google’s IdP Information

Google will now display:

  • SSO URL
  • Entity ID
  • Certificate (X.509)

📤 Send these three values to your Arthur contact or Keycloak administrator.

They will configure them inside Keycloak to establish trust between Google and Keycloak.

Then click Continue.


Step 4 — Enter Arthur’s Keycloak Information

On the next screen, fill in the service provider details exactly as follows:

FieldValue
ACS URL (Assertion Consumer Service URL)https://<auth-endpoint>.arthur.ai/realms/openwebui/broker/google/endpoint
Entity IDhttps://<auth-endpoint>.arthur.ai/realms/openwebui
Start URL(Leave blank)
Signed Response✅ Checked
Name ID formatEMAIL
Name IDBasic Information > Primary Email

Then click Continue.


Step 5 — Add Attribute Mappings

This section defines what user information is sent to Keycloak.

Add the following mappings:

Google Directory AttributeApp Attribute
Primary Emailemail
First NamefirstName
Last NamelastName
GroupsGroups

Tip: The Groups attribute is what enables role mapping (e.g. admin/user) inside Keycloak.

Click Continue.


⚙️ Step 6 — Add Group Memberships (for Admin/User roles)

You’ll now see a section titled “Group membership (optional)”.

This is where you define which Google Groups get sent to Keycloak.

  1. Under Google groups, click the field and add:
  1. Under App attribute, type: Groups

Example configuration:

Google groupsApp attribute
[email protected], [email protected]Groups
  1. Click Finish

Step 7 — Assign Access

By default, your new SAML app is off for everyone.

To allow users to log in:

  1. Go to the app you just created under Apps → Web and mobile apps
  2. Click the new Open WebUI (Arthur) app
  3. Under User Access, set: ON for everyone or restrict to specific organizational units (OUs) if needed.

Step 8 — Send Information to Arthur (Keycloak Admin)

Provide your Arthur contact or Keycloak admin with the following information:

ItemDescription
SSO URLFrom Step 3
Entity IDFrom Step 3
X.509 CertificateFrom Step 3
Admin Group(s)e.g. [email protected]
User Group(s)e.g. [email protected]

Arthur’s team will configure these inside Keycloak to complete the connection.


How Keycloak Uses This Information

Arthur’s Keycloak admin will:

  1. Create two realm roles: admin and user
  2. Add mappers in Keycloak that translate Google Groups → roles:
  1. Test logins from both groups to confirm correct role assignment.

When a user logs into Open WebUI via Keycloak:

  • If they belong to the admin group, they’ll get full admin privileges.
  • If they belong to the user group, they’ll get standard user access.

Summary

StepAction
1Go to admin.google.com
2Add Custom SAML App → name it Open WebUI (Arthur)
3Copy Google IdP details (SSO URL, Entity ID, Certificate)
4Enter Arthur’s Keycloak ACS URL and Entity ID
5Map attributes: email, firstName, lastName, Groups
6Add Google groups → set App Attribute to Groups
7Turn app ON for everyone
8Send information + group names to Arthur for Keycloak mapping

Example Group Design (Recommended)

Group NameExample AddressPurpose
OpenWebUI Admins[email protected]Members become Open WebUI admins
OpenWebUI Users[email protected]Members become regular users

These groups can be managed directly by your organization’s IT team to control Open WebUI permissions dynamically — no need for Arthur to change anything.


End Result

Google GroupKeycloak RoleOpen WebUI Access
[email protected]adminFull admin privileges
[email protected]userStandard user access
(no group match)(optional default user role)Basic user access

That’s it! Your organization is now configured to use Google SAML SSO for Open WebUI via Arthur’s Keycloak. All role assignments are fully automated through your existing Google Groups.