This article includes step-by-step instructions for configuring SAML-based single sign-on (SSO) settings in Google Workspace. For end users, you can integrate with Google Workspace to enable SAML-based SSO for Automated Device Enrollment (with an Enrollment Customization SSO authentication pane), Device Enrollment (also known as "user-initiated enrollment"), and Jamf Self Service for macOS.
While SAML-based SSO for administrators remains supported, Jamf recommends OIDC-based SSO through Jamf Account as a preferred authentication solution. OIDC-based SSO through Jamf Account offers seamless login across Jamf products and access to platform capabilities like blueprints and compliance benchmarks. End-user authentication for enrollment and Self Service can continue using SAML after transitioning administrator authentication to OIDC. For details on implementing OIDC-based SSO, see SSO with OIDC Through Jamf Account in the Jamf Pro Documentation.
Some setting names were changed in Jamf Pro 10.13.0. If you are using an earlier version of Jamf Pro, the setting names will not match the updated names in this article. For a list of name changes, see the 10.13.0 version of the Jamf Pro Release Notes.
Setting up SSO may require simultaneous configuration between Google Workspace and Jamf Pro to ensure some settings are mapped correctly. Additional settings or steps may also be required. See the Single Sign-On section of the Jamf Pro Documentation for Jamf Pro-specific requirements and instructions.
Jamf Pro user accounts or groups that have matching users or groups in Google Workspace
Administrative privileges to Jamf Pro and Google Workspace
For instructions on enabling SSO in Jamf Pro, see the Enabling Single Sign-On in Jamf Pro procedure in the Single Sign-On section of the Jamf Pro Documentation.
Jamf Pro users or end users using enrolled devices may encounter login errors if the Token Expiration Time Override setting is enabled in Jamf Pro. To prevent these errors, you may want to disable the Token Expiration Time Override setting. This will stop Jamf Pro from verifying the token's lifetime, which is controlled by and verified by your IdP. Alternatively, you can ensure that the token expiration time set in Jamf Pro exceeds the expiration time configured by your IdP. However, issues may still occur if the token expiration time dynamically changes.