Why spend countless weeks or months every time you need to implement a new SAML connection?

SSO Easy's EasyConnect SAML solutions eliminates the time, cost, complexity and risk of SAML implementations.

October 2010

Google Apps SAML 2.0 Single Sign On (SSO) Kerberos Support

Few 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 a security token.  That security token is known as a Kerberos ticket.

Many of these same users, and countless more to come in the future, are using Google Apps.

Google Apps offers the promise of cost savings for the organization, while providing the potential to increase user productivity and improve sharing of information among users through the organization.

The promise of Google Apps can only become reality, however, is user adoption is very high.  Providing Single Sign On support for

Google Apps users dramatically increases user adoption, and helps ensure that the goals of a Google Apps implementation will be realized.

In order for an organization to provide SSO function to Google Apps, Google requires adherence to the SAML 2.0 specification and standards protocol.

As an attractive implementation option, more and more organizations are embracing the optional model of leveraging the Kerberos ticket that users generate when logging on their Windows machine each morning, as a preferred mechanism for enabling seamless SSO support to Google Apps.

Tags: Google Apps SSO, IWA SAML, IWA SAML 1.1, IWA SAML 2.0, Kerberos SAML, Kerberos SAML 1.1, Kerberos SAML 2.0, Kerberos SSO, SAML

Google Apps SAML 2.0 SSO – Easy, Fast, Low Cost

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:

  1. The desire to improve personal productivity of users, and
  2. The desire to improve collaboration among users, groups of users, and between business partners

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.

Tags: Google Apps SAML, Google Apps SAML 2.0, Google Apps Single Sign On, Google Apps SSO, Google SAML, Google SAML 2.0, Google SSO

Can You Afford Free Open Source SAML 2.0 & 1.1 Tools?

When looking to implement a SAML solution, the following things need to be considered as part of the decision making process:

  • Type of use case enabled
  • Complexity of the implementation
  • Number of SAML connections
  • Time required to implement a connection
  • SAML expertise required
  • Programming resources required
  • SourceTarget application modifications
  • Maintenance effort
  • Maintenance responsibility

With many different options available in the marketplace, invariably it comes to building a solution (using open source libraries or toolkits) versus buying a turnkey product from a vendor.  If consider the above list, when you are evaluating “Build vs. Buy” ROI analysis, here is what you will most likely come up with:

  Turnkey Product SAML Toolkit/Build Approach
Type of use case enabled Advanced Simple
Complexity of the implementation Low High
Number of SAML connections Multiple One
Time required to implement a connection Low High
SAML expertise required Low/None High
Programming resources required 10% High
SourceTarget application modifications Minimal/Low Touch Significant
Maintenance effort Low/None High
Maintenance responsibility Vendor You
Tags: Open Source SAML, Open Source SAML 1.1, Open Source SAML 2.0, SAML 1.1 Cost, SAML 2.0 Cost, SAML 2.0 ROI, SAML Cost, SAML ROI

Google Apps SAML 2.0 SSO Integrated Windows Authentication

Integrated Windows Authentication is a Microsoft security product.  When users login to a Windows desktop each morning, providing their ID and Password, Microsoft’s Integrated Windows Authentication security product helps to manage the process.

More and more Windows users are using Google Apps, and most organizations that are implementing Google Apps are also looking to provide support for Single Sign On (SSO) function to Google Apps for their users.

Adherence to the SAML 2.0 standards protocol is required by Google in order to facilitate support for SSO to Google Apps.

As an optional deployment solution, many organizations desire to leverage the security information that is captured by Microsoft’s Integrated Windows Authentication security product as the means by which they can trigger SSO for its users accessing Google Apps.

Tags: Google Apps SSO, Google Apps SSO IWA, Integrated Windows Authentication SAML, IWA SAML, IWA SAML 1.1, IWA SAML 2.0, SAML 2.0

Case Study: Google Apps SAML 2.0 Single Sign On – Amazon EC2

Recently, an SSO Easy client successfully implemented a SAML 2.0 Single Sign On (SSO) connection to Google Apps.

What was especially interesting about the representative case study was that, in line with the client’s preferred deployment model, the EasyConnect SAML solution from SSO Easy was deployed by the client on the Amazon EC2 platform.

The implementation was completed virtually instantly, with no implementation issues of any kind.

Tags: Google Apps Single Sign On, Google Apps SSO, Google Apps SSO Amazon EC2, Google Apps SSO Cloud, SAML Case Study Google, SSO

Archives by Subject

Tag Cloud

Please fill out the form below to learn more about our solutions