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.

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.

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.