The current client-side implementation of Janrain integration doesn't work properly on IE10 (and possibly other versions). It properly pops the dialog and the 3rd party login works, but there is a permissions error when the dialog tries to communicate with the opener via JS. Putting IE10 in compatibility mode (at least for the login page) resolves the issue, but then there is a persistent nagbar about the browser being "ancient" (not that we would ever ask users to switch modes anyway). We have not observed any issues in Chrome.

A cursory look through the client-side integration shows that it is significanly different from what the docs recommend, which could be possibly due to them changing the model since implementation and/or the current implementation offering a better solution for mojoPortal. However, not working on IE10 is a showstopper, and I was surprised to see that there weren't any posts about this in the forum. We haven't changed anything in terms of the implementation, and it's difficult to determine if there's a clean way to do it. I'm also not sure if using their recommended approach would even resolve the issue. Trying it out on their test page worked as expected, so it's also possible it may have to do with the document definition since IE may treat permissions differently for the sake of compatibility.

Any thoughts?

I dug in a little more and it looks like the Janrain UI was getting rendered using the iframe model instead of the "janrainEngageEmbed" div one. After some source spelunking I found that adding a key for "OpenIdRpxUseOldImplementation" and setting it to "False" fixed our issue by using the new Janrain implementation.