The Identity-as-a-Service market has a lot of players, and just recently the space has been forced to make room for one more. With their recent acquisition of Bitium, Google IDaaS is now a full on first generation IDaaS solution. Companies like OneLogin, Okta, and Ping Identity are now in direct competition with Google. So let’s take a look at Google IDaaS vs Ping Identity.
A Look at Google IDaaS vs Ping Identity
For IT admins, Google IDaaS is an interesting development – especially for organizations that are already using Google services such as G Suite and therefore have an existing directory of Google identities.
Many of these organizations are currently leveraging Ping Identity and paying a great deal of money for the solution. Ping Identity was created in 2001 with the purpose of sitting on top of Active Directory and connecting AD environments to web-based applications. Okta and OneLogin followed soon after, as it became increasingly obvious that IT was facing serious new challenges with securing identities in their AD environment and connecting those to web applications.
For a long time, if you needed web-application SSO, you were stuck adding an additional solution like Ping Identity into your environment, and paying the extra costs associated with that. Now, it would seem that Google identity management services will now include web application single sign-on for free. IT organizations may be able to eliminate Ping Identity, Okta, or OneLogin in favor of Google identity management. So what is Google’s strategy, and can Google replace the core identity provider?
Google IDaaS and The Core Identity Provider
Google’s strategy in the IAM space has been focused on being an adjunct to the on-prem identity provider, Microsoft Active Directory®. Up until now, Google’s G Suite directory has largely been a user management system for Google Apps and Google Cloud Platform. Now with the acquisition of Bitium, it is a full-on first generation IDaaS platform for web single sign-on.
While a Google Cloud Identity can now access a wide range of web applications, it still isn’t a replacement for the core identity provider, and neither is Ping Identity. When it comes to Google IDaaS vs Ping Identity, both fall short in connecting users to their systems (Windows, Mac, Linux), cloud and on-prem servers (AWS, Azure, on-prem), physical and virtual storage solutions (e.g. Samba file servers and NAS appliances), on-prem applications via LDAP, and wired and WiFi networks through RADIUS.
Replace AD by Integrating Google IDaaS with JumpCloud
The good news is that a tightly integrated solution to G Suite directory is replacing on-prem identity providers like Active Directory. Called Directory-as-a-Service®, this cloud identity management platform serves as the cloud identity provider and federates identities to Google’s identity management services which in turn leverages the identity for web application SSO.
Google IDaaS vs Ping Identity will be an interesting battle to watch, as will it be with Google IDaaS and Okta and OneLogin. The first generation IDaaS space will be more active and interesting now for IT organizations.
Learn More about Replacing Your On-Prem Core Identity Provider
Learn more about a cloud Active Directory alternative by reading how Rock Island-Milan School District replaced AD and is enjoying a seamless integration with G Suite. To learn more about the architecture behind our Google IDaaS integration, consider watching the whiteboard video below.
If you would like more information about connecting users to their systems, servers, applications, networks, and file servers please drop us a note. We also encourage you to start testing our G Suite integration and all of our features by signing up for a free account. Your first ten users are free forever.
This is a Security Bloggers Network syndicated blog post authored by Natalie Bluhm. Read the original post at: JumpCloud