Pages

Tuesday, 7 May 2013

Loop-back when you use SAML to log into CHROME

Having looping issues with SAML and Google?

Our users like signing in to Chrome because it allows them to share bookmarks and extensions on multiple devices. But sometimes, when they try  and sign-in, SAML sends them into an infinite loop.

The reason is that Chrome is trying to open a Pop-up to ask permission to do this and by default, pop-ups are blocked.

Un-block pop-ups and you fix the problem.

It's under settings, privacy, content settings.

SORRY.... False alarm. That doesn't work. Still need a fix for this problem..


Good question!
When you log into the Chrome browser, you allow your machine to be "managed" by the Chrome management console. In a school setting, it means you inherit  a whole heap of APPs pre-installed by your admin. This is great if the school is purchasing apps in bulk for student use. They can be pushed to all users via the ADMIN dashboard. Users need to be logged in to Chrome to get the apps.... The other big advantage is that  if the user logs on to a different machine and then logs into Chrome, (eg their home machine), they get exactly the same apps and shortcuts....



So what is the downside?....
To get the benefits, you have to agree to:


If you are a Chromebook school, all student devices are managed via the Admin console. In fact the admin push down proxy settings, wireless keys, apps, and a whole heap of other stuff. A non-chromebook using the Chrome browser doesn't get the same degree of management when the user is logged in to Chrome....