Google Workspace SSO for Jumpserver

I need every Jumpserver login in our environment to flow through Google Workspace (Basic edition) so users authenticate once with their Google accounts and land straight inside Jumpserver. CAS (Central Authentication Service) is the protocol I’d like to rely on for this.

At the moment I’m not entirely sure whether a CAS server is already running, so the work begins with a quick audit of the current stack. If there’s no existing instance, I’ll depend on you to deploy a production-ready CAS server, link it to Google Workspace for primary authentication, secure it with HTTPS, and expose the necessary endpoints.

After the CAS endpoint is confirmed, Jumpserver must be configured to delegate authentication to it. The end result should be a smooth SSO flow: users click “Login with Google,” pass through Google’s consent screen, and return to Jumpserver with a valid session—no local passwords needed. User attributes (email, display name) have to map cleanly, and any group or role provisioning that Jumpserver supports should be documented.

Deliverables
• A fully working Google Workspace → CAS → Jumpserver SSO chain, demonstrated live
• Clear, step-by-step documentation of every configuration change and command used, suitable for future maintenance or rollback
• A short knowledge-transfer session (live or recorded) so my team can manage the setup on its own

Let me know which tooling you prefer for the CAS deployment (Docker image, standalone Tomcat, Kubernetes, etc.) and how long you expect the integration to take.