Healthcare customers require innovative support for their SAML 2.0 Single Sign On (SSO) projects and use cases.

A recent SSO Easy healthcare customer needed to deploy a SAML 2.0 solution involving integrated support for Google Apps, Salesforce, and OpenID.

The customer was able to support these unique requirements with the EasyConnect SAML 2.0 Single Sign On (SSO) solution from SSO Easy.  All required function was provided out-of-the-box with the EasyConnect product.

The healthcare client was able to deploy the required solution in about a day

Amazon EC2 has captured enormous market share and interest as many organizations look to leverage the benefits of running various services in the cloud.

At the same time, Google Apps has generated mass appeal for many organizations who hope that Google Apps will help them save money, increase user productivity and foster collaboration.

Single Sign On (SSO) for Google Apps is a key component of any Google Apps rollout strategy.  Simply put, Single Sign On to Google Apps increases user adoption and the resulting collaboration associated with the use of Google Apps.

Google requires SAML 2.0 compliance for support of SSO to Google Apps.

With ever-growing frequency, more organizations are looking to support SAML 2.0 based Single Sign On to Google Apps, while having the option of deploying the SAML 2.0 SSO service solution running on the Amazon EC2 platform.

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.

Cloud based Single Sign On is desired by a number of SSO Easy clients.  A relevant case study involves the implementation completed by a recent SSO Easy client, where they implemented a SAML 2.0 Single Sign On (SSO) connection to Google Apps.

In this particular case study, the client’s preferred deployment model included running the EasyConnect SAML solution from SSO Easy in the cloud.

The client went into production in just a few hours.

A recent client implemented an innovative SAML 2.0 use case using the EasyConnect SAML product solution from SSO Easy.

The case study of the customer’s use case involves users in their organization leveraging their Google Apps login credentials to gain access to Salesforce, leveraging OpenID.

Users first gain access to Google Apps using their Google Apps ID and Password.  In this instance, Google Apps is essentially acting as the Identity Provider (IDP) in the SAML 2.0 implementation.

Once the Single Sign On (SSO) connection to Google Apps has been enabled, the OpenID capability in the EasyConnect product from SSO Easy is enabled to provide seamless SSO access to Salesforce.