How to Emit Your Google Apps Identities via LDAP

Written by Greg Keller on November 12, 2015

Share This Article

If your organization is leaning into the cloud and leveraging Web applications, Google Apps is likely one of the solutions in your arsenal. In fact, Google Apps is a central part of many organizations. Over six million businesses are leveraging Google Apps with over sixty million users.

Google Apps Needs a Partner

As IT admins have learned, Google Apps is not a directory service like Microsoft’s Active Directory. In the past, IT organizations would leverage both Microsoft Exchange (email) and Active Directory (directory services) as a combined, core solution for their infrastructure. When these organizations moved to Google Apps, they struggled to manage their user identities. This is particularly the case if those identities need to be connected via LDAP to devices or applications. Google Apps does not provide a mechanism to use identities stored within Google Apps to connect via LDAP to devices and applications.

If your organization would like to leverage the same credentials that are used within Google Apps for other devices and applications there is a way to accomplish that. It starts with a cloud-based directory solution called Directory-as-a-Service (DaaS). It works like this: an organization’s identities are either imported or created within the cloud-based directory. Those identities are then federated to Google Apps. Users can be provisioned, deprovisioned, or modified as needed. The core identity lives within DaaS, and a copy is securely provided to Google Apps. That same identity can be leveraged via the LDAP protocol as well.

Cloud-based Directory Covers All Identity Bases

Devices and applications seeking to authenticate via LDAP simply connect to an LDAP server provided by the DaaS platform. DaaS does the heavy lifting of translating the identity to work with LDAP or Google Apps. Furthermore, the same identity can be leveraged for devices including Mac and Windows machines or even Linux servers housed at AWS or Google Compute Engine.

By utilizing a Directory-as-a-Service platform along with Google Apps, organizations get what they used to have – a tightly integrated combination of email and directory services. Except, now the solutions are based in the cloud and are delivered as a service without the heavy lifting of on-premises software solutions.

A Closer Look at Directory-as-a-Service

If you would like to learn more about how you can effectively use the same identity for your LDAP devices and applications as well as Google Apps, take a look at Directory-as-a-Service. You’ll simplify your identity and access management approach. Drop us a note. We’d be happy to discuss this further with you, or feel free to give JumpCloud a try.

Continue Learning with our Newsletter