G Suite (formerly Google Apps for Work) is currently one of the hottest IT platforms. Competing heavily with Microsoft Office 365, email hosting and productivity applications are a critical part of any IT environment.
Today, Google Apps has over 5 million businesses using their platform. O365 claims even more. As G Suite becomes a part of more organizations, one challenge that IT admins face is how to integrate GApps identities into their IT environment. The Identity-as-a-Service function for G Suite integration is solving the problem of central user management leveraging Google Apps identities.
Google Apps Directory Service in a Nutshell
Google Apps does have a directory. Unfortunately, Google Apps directory service is essentially a contact database that helps IT manage a user’s access to their Google Apps services. It also has the ability to authenticate via OAuth and SAML for a few other web properties.
However, it does not function as a true cloud identity provider. In short, G Suite directory is not a replacement for the traditional directory services Microsoft Active Directory and OpenLDAP.
Crack The Code of G Suite Integration
A new generation of cloud identity management platform called Directory-as-a-Service® is effectively an Active Directory replacement from the cloud. It serves as a central, authoritative directory service across systems, applications, and networks. The Identity-as-a-Service platform is tightly integrated with Google Apps, thus enabling users to leverage their Google Apps identities across virtually their entire infrastructure. With the unified cloud directory, the same credentials that a user leverages for their GApps login is also used for their macOS laptop, Windows desktop, or Linux server hosted at AWS. In addition, the virtual identity provider can leverage GApps credentials for WiFi authentication.
The benefit for IT organizations is to be able to shift their entire infrastructure to the cloud. By selecting G Suite, an organization is looking to move their email infrastructure to the cloud and to leverage cloud productivity applications. Without a cloud directory service, though, IT is stuck with an on-prem, legacy directory service. And that usually means Active Directory or OpenLDAP. That approach essentially forces the organization to have one foot in the cloud and one foot on-prem. And that defeats the purpose of moving to the cloud. Directory-as-a-Service solves the issue by moving the identity provider to the cloud as well as tightly integrating with G Suite.
Drop us a note to learn more about the Identity-as-a-Service function for G Suite integration. Alternatively, sign up for a free account to test the integration between Directory-as-a-Service and Google Apps yourself. Since your first 10 users are free forever, get started today!