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.