-
Notifications
You must be signed in to change notification settings - Fork 374
google workspace oidc doc #1908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Muhammadsaeed707
merged 2 commits into
huggingface:main
from
Muhammadsaeed707:google-workspace-oidc
Sep 10, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| # How to configure OIDC SSO with Google Workspace | ||
|
|
||
| In this guide, we will use Google Workspace as the SSO provider with the OpenID Connect (OIDC) protocol as our preferred identity protocol. | ||
|
|
||
| We currently support SP-initiated authentication. User provisioning is part of Enterprise Plus's [Advanced SSO](./enterprise-hub-advanced-sso). | ||
|
|
||
| <Tip warning={true}> | ||
| This feature is part of the <a href="https://huggingface.co/enterprise">Team & Enterprise</a> plans. | ||
| </Tip> | ||
|
|
||
| ### Step 1: Create OIDC App in Google Workspace | ||
|
|
||
| - In your Google Cloud console, search and navigate to `Google Auth Platform` > `Clients`. | ||
| - Click `Create Client`. | ||
| - For Application Type select `Web Application`. | ||
| - Provide a name for your application. | ||
| - Retrieve the `Redirection URI` from your Hugging Face organization settings, go to the `SSO` tab and select the `OIDC` protocol. | ||
| - Click `Create`. | ||
| - A pop-up will appear with the `Client ID` and `Client Secret`, copy those and paste them into your Hugging Face organization settings. In the `SSO` tab (make sure `OIDC` is selected) paste the corresponding values for `Client Identifier` and `Client Secret`. | ||
|
|
||
| <div class="flex justify-center"> | ||
| <img class="block dark:hidden" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/sso/sso-google-oidc-create.png"/> | ||
| <img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/sso/sso-google-oidc-create-dark.png"/> | ||
| </div> | ||
|
|
||
| ### Step 2: Configure Hugging Face with Google's OIDC Details | ||
|
|
||
| - At this point the **Client ID** and **Client Secret** should be set in your Hugging Face organization settings `SSO` tab. | ||
| - Set the **Issuer URL** to `https://accounts.google.com`. | ||
|
|
||
| <div class="flex justify-center"> | ||
| <img class="block dark:hidden" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/sso/sso-google-oidc-hf-details.png"/> | ||
| <img class="hidden dark:block" src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/hub/sso/sso-google-oidc-hf-details-dark.png"/> | ||
| </div> | ||
|
|
||
| ### Step 3: Test and Enable SSO | ||
|
|
||
| <Tip warning={true}> | ||
| Before testing, ensure you have granted access to the application for the appropriate users. The admin performing the test must have access. | ||
| </Tip> | ||
|
|
||
| - Now, in your Hugging Face SSO settings, click on **"Update and Test OIDC configuration"**. | ||
| - You should be redirected to your Google login prompt. Once logged in, you'll be redirected to your organization's settings page. | ||
| - A green check mark near the OIDC selector will confirm that the test was successful. | ||
| - Once the test is successful, you can enable SSO for your organization by clicking the "Enable" button. | ||
| - Once enabled, members of your organization must complete the SSO authentication flow described in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's reorder okta and azure to have each one with saml/oidc options? ie make ordering consistent