gapi.auth.authorize does not work in Windows 8 metro-style IE

[wonderfly]

From lostfree...@gmail.com on March 18, 2013 21:58:45

After call to gapi.auth.authorize, new tab is opened, where you can enter credentials.

Expected:

• after entering valid credentials tab should close itself
• authorization callback should be fired
• app should become authorized (next call to authorize with immediate = true should report this)

Actual:

• tab remains opened with blank page
• authorization callback is not fired
• app is still not authorized

Original issue: http://code.google.com/p/google-api-javascript-client/issues/detail?id=76

[wonderfly]

From lostfree...@gmail.com on March 18, 2013 22:00:54

This happens on the web site.

[wonderfly]

From aquap...@gmail.com on June 10, 2013 00:39:52

any news?

[wonderfly]

From basketca...@gmail.com on September 04, 2013 04:00:31

This is preventing our website from being used on Win8 machines - any update on this issue would be greatly appreciated.

[wonderfly]

From napasc...@gmail.com on September 24, 2013 09:29:07

any workaround?

[wonderfly]

From brian.ke...@gmail.com on April 29, 2014 08:52:35

Experiencing a similar issue on Windows Phone 8 with "gapi.client.load"

[wonderfly]

From tom.r...@gmail.com on July 25, 2014 06:01:06

This issue is affecting from releasing my app which uses this client framework for authenticating into Google API, might have to redo my work using a server solution.

[wonderfly]

From benoit.p...@gmail.com on July 25, 2014 06:39:57

Hi Tom, I had a similar issue for my app For Office Keluro Web Analytics That you can download try and rate five stars here^^ http://goo.gl/MkOtSH Regarding your problem. Do not use a server solution, you want to stay with a useragent flow. In addition, you probably do not want to manipulate your customer credentials (you may loose a lot of non trusting end-user). Trick was there are many browser security restrictions (see http://goo.gl/77zRUd ) that prevents the interframe communication process of the googleAPI. However, this was not a serious business to rewrite the OAuth2 flow according to google specifications ( http://goo.gl/pi09PK ). I should have done this on the first place, I lost a lot of time. I did it and its well cross browser. I was thinking to give the snippets on my blog (www.benoitpatra.com) but the post is not written yet...

[wonderfly]

From tom.r...@gmail.com on July 25, 2014 06:47:35

That totally worked Benoit, thanks a bunch.

[wonderfly]

From bsittler@google.com on July 29, 2014 12:05:08

Is this behavior appearing in regular Metro Internet Explorer, or in a separate stand-alone application that uses an embedded browser component, or both? Also, what CPU architecture, Windows version, and IE version are you seeing this behavior in? Attempts to reproduce this issue have so far been unsuccessful.

[wonderfly]

From benoit.p...@gmail.com on July 29, 2014 12:50:00

Hi, actually (to my knowledge) it's not a matter of IE version or OS version. Indeed, I found out that the culprit comes from security config which default settings change when shipped with windows 8.1 metro style see my comments in the issue #120 ( http://goo.gl/bhrxow )

In addition, there is also a situation when you try to use the google javascript API in a sandboxed environment (the html5 iframe with sandbox attributes) which is the case in some of windows App model (for Office at least). It took me a lot of time to figure the in-and-outs, but for the situation mentioned in the first paragraph there is no iframe involved.