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.

Tag: Kerberos SSO

Google Apps SAML 2.0 Single Sign On (SSO) IWA support

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.

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

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

Google Apps is being rolled out to countless users and organizations each day.

For many various reasons, Single Sign On (SSO) access to Google Apps is desired by those organizations.  Google requires compliance with the SAML 2.0 security protocol in order to provide support for Single Sign On into Google Apps.

From the user perspective, they do not want an awkward, intrusive, difficult, or time-consuming experience.  In short, they want to be able to operate and act as they always have done in the past.

Innovative IT organizations have recognized that these users are accustomed to (and widely accept) the notion that they need to sign in to the desktop machine each day, providing an ID and a Password.

These innovative IT organizations have embraced the optional deployment model of leveraging the ID and Password that the user provides when logging in to his desktop each morning, as the mechanism for triggering SAML 2.0 based Single Sign On (SSO) to Google Apps.

Tags: Desktop SAML, Desktop Single Sign On, Desktop SSO, Integrated Windows Authentication SSO, IWA SSO, Kerberos SSO, SAML SSO

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

Archives by Subject


Tag Cloud

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