SSO Easy's EasyConnect SAML solutions eliminates the time, cost, complexity and risk of SAML implementations.
Recently, a school based in Ohio implemented the Google Apps Single Sign On solution from SSO Easy, using the EasyConnect product. EasyConnect makes implementing all SAML 2.0 and SAML 1.1 projects quick, easy, and cost effective.
Despite having no substantial IT infrastructure and no prior SAML experience, in this representative SSO Easy case study, the school was able to to live with the solution for 1,300 users in just a few hours.
A major university based in the US recently successfully implemented EasyConnect, the SAML 2.0 Single Sign On (SSO) software product from SSO Easy.
In this representative case study, the university implemented EasyConnect after first failing with their own extensive attempts at custom coding a SAML 2.0 solution for Google Apps using Open Source SAML toolkits.
Once they selected SSO Easy’s out of the box Google Apps software product solution, they successfully deployed the solution to their entire Google Apps user population without any issues or delays.
The university successfully rolled out Google Apps, with SSO Easy’s Single Sign On product for Google Apps to 4800 users, leveraging the university’s existing Active Directory implementation.
Not too many users are aware that when they sign on to their Windows desktop in the morning, by providing their main ID and Password to the machine, they are generating accessing a Windows security function called IWA.
Google Apps is being rolled out to many of these same users, and, for a variety of reasons, Single Sign On (SSO) function is needed or wanted for those users. Google requires implementation of the SAML 2.0 standards protocol in order to enable Single Sign On to Google Apps.
More and more organizations desire the option of leveraging the IWA security information that is generated by the user when login to the Windows desktop is completed as the main mechanism for enabling SSO support to Google Apps.
Google Apps has generated mass appeal for organizations world-wide. The hope is that Google Apps will help the deploying organization money, while increasing user productivity and increasing organizational collaboration.
Enabling support for Single Sign On (SSO) for Google Apps is a core and vital component of any Google Apps rollout strategy. The premise is simple:
SAML 2.0 compliance is required by Google in order to facilitate and support SSO to Google Apps.
At the same time, the marketplace is captured by the allure of the option of running services in the cloud.
More and more organizations are looking to leverage SAML 2.0 based Single Sign On to Google Apps, while having the option of deploying the SAML 2.0 SSO service solution in the cloud.
Many organizations throughout the world have implemented Google Apps. Analysts’ estimates indicate that countless more will deploy Google Apps in the coming years.
Two of the main goals associated with the deployment of Google Apps are:
Personal productivity and collaboration benefits can only be achieved if the Google Apps platform is easy to use, secure, and readily accessible. Single Sign On capability is needed in order to provide such seamless access and use of Google Apps.
Google requires the SAML 2.0 protocol in order for organizations to provide support for SSO to Google Apps.
For many organizations, the process of enabling support for SAML 2.0 based Single Sign On capability and access to Google Apps has resulted in a difficult, painful and costly effort.
In order for users, organizations, and the marketplace to realize the key intended benefits of Google Apps, the implementation of SAML 2.0 based SSO to Google Apps must become a fast, easy, low cost process for all organizations.