By Vince Lujan Posted July 14, 2018
Google Cloud Platform™ (GCP) has become a popular alternative to AWS® and Azure®. All three platforms have become quite successful, and IT organizations are shifting their server infrastructure to the cloud. The question for IT admins as they move to a hybrid cloud/on-prem environment is how to make Google Cloud server authentication actually work.
Why Manage Access to Google Cloud Servers?
Managing user access to servers has always been a critical task. As a result, whole categories of solutions have been created around it, such as privileged identity management tools. When the data center was on-prem or connected to the core IT infrastructure via VPN, Microsoft® Active Directory® (AD) would often provide the server authentication function. Yet, as the on-prem server infrastructure moved to the cloud, challenges arose.
One of the major challenges was how to control user access to cloud servers. The on-prem identity provider, usually Active Directory, didn’t easily extend to the cloud. Active Directory also worked on the model of direct connect, where a server needed to have a direct pathway to AD to authenticate user access. This was accomplished via VPNs and dedicated network connections. As the server infrastructure moved away into the cloud, however, the concept of direct access to Active Directory was much more difficult. IT organizations and DevOps engineers would end up having to create additional VPNs, and networking the cloud servers to the on-prem AD instance wasn’t easy.
In the end, that approach ended up being quite painful. IT admins and DevOps engineers started to fall back to other options—manual user management and configuration management tools. Both of these were obviously less than ideal. So, while moving the server infrastructure to an IaaS platform such as Google Cloud Platform is valuable, it can cause problems with cloud server authentication.
Google Cloud Server Authentication and More
The good news is that there is a modern cloud identity management platform that seamlessly integrates with Google Cloud Platform to help solve this problem. It’s called JumpCloud® Directory-as-a-Service®, and it is essentially the holy grail when it comes to modern directory services platforms. With JumpCloud, IT admins don’t need to have multiple authentication silos or choose between the lesser of the evils. Instead, this centralized cloud identity provider solves the Google Cloud server authentication problem and a whole lot more.
For example, users can be authenticated to Google Cloud Platform servers, whether Linux® or Windows, via core JumpCloud identities. Additionally, those same identities can also be leveraged for on-prem systems (Windows, Mac®, Linux), on-prem servers or those at other cloud infrastructure providers such as AWS or Azure, web and on-prem applications via SAML and LDAP, cloud and on-prem storage solutions such as Samba file servers and NAS appliances, and wired and WiFi networks through RADIUS. As a result, IT admins can enjoy a centralized identity and access management platform that can authenticate users to virtually any IT resource, including Google Cloud servers and a lot more.
Learn More About JumpCloud Directory-as-a-Service
Sign up for a free account to see the full functionality of the JumpCloud Directory-as-a-Service platform in action. We offer 10 free users (free forever) to help you get started. Schedule a demo with us and we can walk you through our Google Cloud server authentication functionality and everything else we offer. Of course, don’t hesitate to contact JumpCloud if you have any questions.