Overview
3DPrinterOS supports Single Sign-On (SSO) through SAML 2.0, including (but not limited) integrations with Shibboleth, Google Workspace, Okta and Microsoft Entra ID (Azure AD).
SAML SSO securely transfers a user’s identity from an Identity Provider (IdP) to 3DPrinterOS, which acts as the Service Provider (SP). Authentication is handled through digitally signed XML exchanges.
Choosing Your SSO Method
Before setting up SSO, determine which option fits your organization’s environment.
Google or Microsoft: Best for K–12 and organizations that already manage users in Google Workspace or Microsoft Entra ID (Azure AD).
Shibboleth / Other SAML2 compatible IdPs: Best for universities and enterprise environments using a dedicated Identity Provider.
If your organization uses Google, follow this separate setup guide:
Google Workspace SSO Integration Guide
Roles
3DPrinterOS acts as the Service Provider (SP) and redirects users to their organization’s Identity Provider (IdP) for authentication.
Integration typically involves exchanging metadata XML files between the IdP and 3DPrinterOS.
3DPrinterOS supports SSO through any Identity Provider that implements the SAML 2.0 protocol, including Shibboleth, Okta, Azure Entra ID, and Google SSO.
Environments
Production (Cloud): https://cloud.3dprinteros.com
All SAML2 / Shibboleth integrations are typically tested and deployed directly in the production environment.
A separate test environment is available upon request but generally not required.
Step-by-Step Integration
1. Exchange Metadata between 3DPrinterOS (SP) and your IdP.
Here is the 3DPrinterOS SP metadata for the production environment:
SP details extracted from metadata:
Entity ID: https://cloud.3dprinteros.com/sp
2. IdP Setup
Import the 3DPrinterOS metadata into your IdP to establish SAML trust.
Microsoft Entra ID (Azure AD): check this guide for more details:
Microsoft SSO Integration Guide
After configuration, send your IdP metadata as an XML file or provide a link to your XML metadata to support@3dprinteros.com. If your IdP is registered in InCommon, you may simply provide your Entity ID.
3. 3DPrinterOS Setup
Once your IdP information is received, the 3DPrinterOS team will configure the SP endpoints and provide a link for verification.
4. Deployment
After successful configuration the SSO login option becomes available in 3DPrinterOS under https://cloud.3dprinteros.com → SSO tab.
Direct sign-in link (IdP-initiated SSO)
IdP-initiated SSO is supported. Once we add your IdP metadata, your organization gets a direct sign-in link in the format https://cloud.3dprinteros.com/ssosaml/<your org key>/auth. You can place this link in your portal so users go straight through SSO into 3DPrinterOS. The org key is generated on our side when your IdP metadata is added, so ask support@3dprinteros.com for your organization's link.
Renewing your IdP signing certificate
When the signing certificate in your identity provider's metadata expires, SSO sign-in stops working until the new one is added on our side. When you renew or rotate the certificate, send your updated IdP metadata to support@3dprinteros.com, either the metadata URL (for Microsoft Entra ID, the App Federation Metadata URL) or the metadata XML file.
Until the new certificate is added, users can sign in with their email and password instead of the SSO button, using Forgot password if they have not set one.
This is the SAML certificate of your identity provider. It is not the HTTPS certificate of the 3DPrinterOS Client described in Configuring HTTPS & External Access for 3DPrinterOS Client.
SAML Attributes
Required attribute: Email
Optional attributes: First Name, Last Name
3DPrinterOS retrieves data using the following attribute mappings (only Email is required).
Email (required):
mail
urn:oid:0.9.2342.19200300.100.1.3
eduPersonPrincipalName
urn:oid:1.3.6.1.4.1.5923.1.1.1.6
First Name (optional):
givenName
urn:oid:2.5.4.42
Last Name (optional):
sn
urn:oid:2.5.4.4
If your IdP uses custom attributes, please provide the claim URIs or short names to ensure correct mapping.
Assigning workgroups and the Organization Admin role from a group attribute
Workgroups and the Organization Admin role can be assigned from a group attribute in the SAML response, such as isMemberOf, each time a user signs in through SSO. The 3DPrinterOS team sets this up for you, and it needs the name of the SAML response attribute to check and a table that shows, for each attribute value, which rule applies and which workgroup names it covers. Send both to support@3dprinteros.com.
Workgroups are not created automatically, so create the workgroups you want the groups to map to in your organization first. A user can be a member of several workgroups at the same time, so groups that overlap do not cause a problem.
Four rules are available.
workgroup_add_or_removeadds the user to the workgroup if the value is present and removes them if it is absent.workgroup_addadds the user to the workgroup if the value is present and does not remove them if it is absent.workgroup_removedoes not add the user to the workgroup if the value is present and removes them if it is absent.orgadmin_add_or_removegives the user the Organization Admin role if the value is present and removes it if it is absent.
The table can look like this example.
Attribute value | Rule | Workgroups |
OrgStaff | workgroup_add_or_remove | Admins |
Students | workgroup_add | StudentsWg, TestPrintersWg |
OrgStaff | orgadmin_add_or_remove |
If an admin who has active printers loses the group behind an orgadmin_add_or_remove rule, their Organization Admin role is removed, all of their printers are taken out of the workgroups they are in, and your users lose access to those printers. If your list of admins stays mostly the same, it is safer to leave this rule out, so that a change to the group on the SSO side cannot affect printer access by accident.
