Directory-as-a-Service Use Case: Integration with G Suite

Written by Rajat Bhargava on November 11, 2016

Share This Article

As organizations have adopted G Suite (formerly Google Apps for Work), a key challenge for IT admins has centered on how to manage those user identities. G Suite does not provide a directory service, and it makes little sense to leverage an on-prem directory service when you have moved your core email and productivity suite infrastructure to the cloud. A primary use case of Directory-as-a-Service® solves this problem and integrates seamlessly with G Suite.

How It Works: Directory-as-a-Service Integration with G Suite

jumpcloud g suite integration

The approach is to provide a central, authoritative directory service delivered from the cloud. The unified cloud directory has the ability to provision, de-provision, sync, and modify user access to Google Apps and a wide variety of other IT resources. If an organization is already using G Suite, it is easy to extend those credentials to be the ones that are used throughout an organization. Directory-as-a-Service imports the users from G Suite into its cloud directory platform. User identities can then be pushed to a user’s laptop or desktop, cloud servers at AWS, SaaS applications, on-prem LDAP-based applications, and the WiFi network as well. A user’s G Suite identity can be leveraged throughout the IT infrastructure.

As new users are added to the organization, those users are created in the Directory-as-a-Service platform. The platform then federates those identities to G Suite and elsewhere. Specifically, with G Suite, the user is automatically provisioned when they are added to the appropriate group. Conversely, when a user needs to be de-provisioned that also occurs from a signal from the Directory-as-a-Service cloud platform. One benefit of this approach is that IT doesn’t need to manage users in many different applications and platforms.

G Suite as The Central Identity

Another benefit of this approach is that the user’s G Suite identity can be the central identity throughout the organization. Directory-as-a-Service can effectively extend those credentials to be the ones that are used for systems, applications, and networks. As a result, this will limit the friction and frustration experienced by end users. That central control gives IT the ability to more securely manage identities across the organization. Access is centrally controlled from the Directory-as-a-Service web console.

Put Identity-as-a-Service to Work for You

If you would like to learn more about how the Directory-as-a-Service use case for integration with G Suite can support your organization, drop us a note. Alternatively, give the Identity-as-a-Service platform a try for yourself. Your first 10 users are free forever.

Continue Learning with our Newsletter