{"id":5318,"date":"2016-10-08T07:00:56","date_gmt":"2016-10-08T13:00:56","guid":{"rendered":"https:\/\/www.jumpcloud.com\/blog\/?p=5318"},"modified":"2023-08-30T14:20:08","modified_gmt":"2023-08-30T18:20:08","slug":"g-suite-single-sign-on-vs-okta-sso","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/g-suite-single-sign-on-vs-okta-sso","title":{"rendered":"G Suite Single Sign-On vs. Okta Single Sign-On"},"content":{"rendered":"\n
One of the recent enhancements to G Suite has been their focus on single sign-on (SSO)<\/a> with a few select applications via SAML. G Suite has leveraged OAuth<\/a> authentication for years, but the most recent enhancement has been <\/span>SSO via SAML<\/span><\/a>. <\/span><\/p>\n\n\n\n Of course, this foray into SAML is directly competitive with our friends at Okta.<\/span><\/p>\n\n\n It seems that Google wants to leverage their <\/span>G Suite directory<\/span><\/a> to authenticate to more than just the G Suite applications. This is creating a situation where IT admins need to decide on which solution is a better fit \u2013 G Suite versus Okta. <\/span><\/p>\n\n\n\n Of course, that\u2019s only for the web application layer \u2013 as IT admins think about centralizing their user management around G Suite identities, <\/span>Directory-as-a-Service\u00ae<\/span><\/a> becomes a very interesting part of the identity management picture. <\/span><\/p>\n\n\n\n G Suite, which was <\/span>formerly known as Google Apps for Work<\/span><\/a>, has a user directory. That user directory has historically just been for GApps services. A few years ago, Google added the ability for other third party sites to leverage the GApps user store for authentication. This happened over the OAuth protocol. <\/span><\/p>\n\n\n\n The idea was to make it easy for third party sites to leverage the credentials within GApps. It also made it easier for end users to sign-up and leverage a web application or service. This approach was limited to the OAuth protocol and web applications or sites. The uptake wasn\u2019t significant because not all of these sites wanted to count on Google for their user\u2019s information (of which very little was passed to the website) and further, not all of their users had Google Apps!<\/span><\/p>\n\n\n\n As a result, Google decided to take their SSO strategy and move it one step further to include the SAML protocol. Google released integrations with about 15 to 20 web applications. While it was a first salvo into the SAML SSO<\/a> market, Google clearly had designs on disrupting the progress that Okta has been making. <\/span><\/p>\n\n\n\n<\/figure><\/div>\n\n\n
G Suite Single Sign-On Takes Aim <\/span><\/h2>\n\n\n\n