Free TrialContact Us

Register Once for Complete Access to OneLogin’s Resource Library

3 IAM Considerations When Implementing Google Apps

Summary

To populate user identities into Google Apps, Google Apps for Work requires integration into the enterprise identity repository via Google Apps Directory Services (GADS). GADS is used to replicate the existing Active Directory or LDAP compliant user identities, and access permissions to the Google Apps domain. IT organizations attempting to secure Google Apps with GADS are often challenged by its limited scalability, delayed on and off-boarding, and lack of desktop Single Sign-On (SSO).

Table of Contents

Introduction

Limited Enterprise Scalability

Directory Synchronization is Network Intensive and Not Real-Time

Desktop Single Sign On Requirements for Windows Environments?

OneLogin is an Enterprise Identity Management Solution for Google Apps for Work

OneLogin Handles Complex Directory Structures

OneLogin Delivers Instant Off-Boarding

OneLogin Delivers Desktop Single Sign On

Conclusion

The limitations of Google Apps Directory Services (GADS) when deployed in an enterprise environment are clear.

  • Please enter first name
  • Please enter last name
  • Please enter company name
  • Please enter number of employees
  • Please enter a valid email address
  • Please enter your phone number
  • Please enter state

  • By completing and submitting this form, I agree to the storing and processing of my personal data by OneLogin as described in our Terms of Service and Privacy Policy.