by SSO Easy
January 31, 2012
In a representative SSO Easy client case study, a customer successfully implemented the EasyConnect product solution. Using EasyConnect, the client was able to achieve its objective of restricting remote access to Google Apps users based on IP Address.
This key function of the EasyConnect product allowed the client to successfully manage selective access to Google Apps for some users who were authorized to access Google Apps when they were outside of the office.
The solution was successfully implemented into production in just a few hours.
For more information about the solution, or to request a Free Trial of this solution, please visit www.ssoeasy.com Free Trials are typically completed in less than 1 hour.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
January 31, 2012
Google Apps customers are able to manage security policy for remote user access to GMail, Google Docs, and all Google Apps features, using the EasyConnect product. This capability is enabled in EasyConnect by allowing Google Apps customers to effectively restrict remote access based on IP Address, or range(s) of IP Addresses.
This function addresses a key security requirement for all Google Apps customers.
This solution is typically implemented in production in just a few hours. Free Trials of the solution are typically completed in less than 1 hour.
For more information, or to request a Free Trial of the solution, please visit www.ssoeasy.com.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
January 31, 2012
SSO Easy provides a solution with its EasyConnect product which supports Google Apps customers who require restricting remote access to Google Apps based on IP Address. This key EasyConnect product feature allows Google Apps to effectively enable security policy for remote users or groups of users.
A Free Trial of the solution may be requested at www.ssoeasy.com Free Trials are frequently completed in less than 1 hour.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
January 31, 2012
SSO Easy provides a solution which allows Google Apps customers to enable restricted access to GApps based on an IP address, or on the basis of a range of IP addresses. This key security policy feature is included with the EasyConnect product from SSO Easy.
For more information, or to request a Free Trial of the solution, please visit www.ssoeasy.com Free Trials of this solution are typically completed in less than 1 hour.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
January 31, 2012
Using the EasyConnect product from SSO Easy, Google Apps customers are able to restrict access to Google Apps by IP Address, or by ranges of IP Addresses. This key EasyConnect function provides clients with the ability to apply advanced security policy for remote users accessing Google Apps.
To request a Free Trial of this solution, please visit www.ssoeasy.com
Free Trials are typically completed in about 1 hour.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
November 25, 2011
Since SAML (what Google uses for SSO) needs a browser in order function properly, alternative clients such as mobile devices can't leverage SAML SSO. Therefore, traditional authentication mechanisms (e.g. user id\password) are required. This becomes a challenge when SSO is enabled within Google because password management by the user within the web UI is disabled.
To allow access for alternative clients, a password needs to be created in Google Apps.
SSO Easy has two options available through its EasyConnect Single Sign On solution for doing this:
1) Allow the user to set a password in Google
The Google Password Updater will allow the user to create a "set and forget" password in Google (an alternative option is to have the Google Password Updater generate a mixed-case alphanumeric random password of a configurable length and strength on behalf of the user). This password is then pushed to Google via the Google API. This method eases password resets for users – they can simply generate a new password at any time in a self-service model.
2) Synchronize AD passwords with Google
When a user goes through the SSO process to access the web based Google Apps, their Active Directory / AD or LDAP password will automatically be sync with Google.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
November 19, 2010
A large US-based university, with almost 5000 users, recently implemented a SAML 2.0 Single Sign On (SSO) solution, along with integrated SSO support for mobile devices / cell phone Single Sign On access to Google Apps.
The university selected EasyConnect, the SAML 2.0 Single Sign On (SSO) software product from SSO Easy, along with the integrated Password Manager, which provides mobile / cell phone SSO integrated function.
This representative SSO Easy case study deployment was implemented without any issues, going into production with just a few days of effort.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
November 11, 2010
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.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
November 11, 2010
Outlook is by far the most prevalent email client being used in the world today. Current estimate ranges indicate that as many as 60% - 85% of all users worldwide utilize Outlook for their email system.
Google Apps is the fastest growing personal productivity platform in the world today. Google has indicated that as many as 3,000 new organizations are deploying Google Apps every day.
From a user perspective, Single Sign On support between and among commonly-used systems is a vital need.
As countless organizations and users migrate from Micrsoft Exchange to Google Apps, many organizations and many users must operate and support a mixture of Outlook and Google Apps. Coexistence of these two dominant platforms is a critical requirement for a growing number of organizations throughout the world.
Enabling SSO between Outlook and Google Apps is now a mandatory requirement in every organization that currently leverages Outlook, and plans to leverage Google Apps.
SAML 2.0 is the de facto standard for enabling secure, standards-based Single Sign On for Google Apps platforms and user communities.
A Single Sign On solution which provides support for SSO with SAML 2.0 and between Outlook and Google Apps is a must-have capability for a growing number of organizations throughout the world today.
If you enjoyed this post, make sure you subscribe to our RSS feed!
by SSO Easy
November 10, 2010
With ever-growing popularity, users and organizations are looking to leverage the promise of Google Apps. The hope of increasing security, increasing user productivity, and improving collaboration among users is extremely attractive to many organizations.
Enabling Single Sign On (SSO) function for Google Apps users is a core component of the overall strategy for organizations who intend to rollout Google Apps to its users.
Google requires adherence to the SAML 2.0 specifications in order to enable support for Google Apps SSO.
A variety of access methods are required in order to effectively address the needs of the wide variety of Google Apps Single Sign On use cases that exist in various environments. One critical option that must be provided lies in the ability to optional support for Form based authentication.
If you enjoyed this post, make sure you subscribe to our RSS feed!
