Skip to main content

Google Workspace SSO Integration Guide

Illia Nazarko avatar
Written by Illia Nazarko
Updated over a week ago

Overview

Choosing Your Login Method

  • SAML (Recommended for managed environments): Centralized authentication using your organization’s Google Workspace.

  • OAuth2 (“Enter with Google Button”): Simple sign-in using existing accounts. No metadata exchange or admin setup required.

If your institution manages logins in Google Admin, use SAML SSO.

If you only need quick access without SAML configuration, use the “Enter with” option.

Google Workspace SSO with SAML2


3DPrinterOS supports SAML-based integration with Google Workspace. This method connects 3DPrinterOS with your Google Identity Provider (IdP) for managed, organization-wide authentication.

Setup Steps

  1. In the Google Admin console, go to Apps → Web and mobile apps → Add app → Add custom SAML app (check the official Google’s SAML documentation for more details: https://support.google.com/a/answer/6087519

  2. Name the app (for example, 3DPrinterOS).

  3. When prompted for Service Provider details, enter:

  4. Download your IdP metadata XML file or copy the metadata URL.

  5. Send your metadata file or URL and Entity ID to support@3dprinteros.com.

  6. The 3DPrinterOS team will configure the Service Provider and confirm activation.

Check the other SSO integration details (section “SAML Attributes” in particular) in the generic 3DPrinterOS SSO Integration Guide

“Enter with Google” button (OAuth2)

This is a quick login option that uses Google OAuth2 authentication instead of SAML.

How It Works

  • Users click the “Enter with Google” button at https://cloud.3dprinteros.com.

  • 3DPrinterOS authenticates them through Google OAuth2 SSO.

  • User details (email, first name, last name) are retrieved automatically.

  • If the email matches your organization’s domain, the user is automatically added to your organization and default workgroup.

Advantages

  • No metadata setup or IdP configuration needed.

  • Ideal for smaller schools or simple deployments.

Limitations

  • No custom attribute mapping.

  • Not a true IdP-managed SSO.

Did this answer your question?