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.

Active Directory is the most common IT repository for storing user credentials and security policies.  IT organizations, for good reason, embrace the idea of this type of effective central management capability for user entitlement information.

Countless organizations are rolling out Google Apps to their users in an effort to reduce costs, improve productivity, and harness the synergy associated with collaboration among users and groups in the organization.  In order to truly benefit from the promise of Google Apps, enabling support for Single Sign On capability is essential.

Google requires that organizations comply with the specifications of the SAML 2.0 protocol in order to enable SSO support.

More and more, organizations who are implementing Google Apps are requiring seamless integration, use and Password sync of credentials that currently reside in Active Directory for enabling SAML 2.0 Single Sign On (SSO) access to Google Apps.

Virtually all of the cost of SAML 2.0 or SAML 1.1 Single Sign On projects are labor-based. 

Costs often are unplanned and grow to become excessive on SAML projects, because companies typically underestimate the scope and complexity of a SAML implementation project.

Buying the right Enterprise SAML Software Product will help to eliminate excess labor costs, and will result in SAML projects that are consistently delivered on time and on budget.

The portion of the overall project cost that is associated with licensing of an Enterprise Software Product for SAML 2.0 and SAML 1.1 deployment projects is a minor cost component associated with these Single Sign On projects.

SAML 2.0 running in the Cloud is desired by a number of SSO Easy clients who are looking to enable SAML 2.0 based Single Sign On capability for their users.

A recent representative case study was completed by an SSO Easy client, where they implemented a SAML 2.0 Single Sign On (SSO) connection to Salesforce.

In this client case study, the client’s preferred deployment model included running the EasyConnect SAML solution from SSO Easy for the purpose of enabling SAML 2.0 based Single Sign On to Salesforce – running in the cloud.

The solution went into production in about 2 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.