Unfortunately, recently I have discovered that NotScripts is breaking the
Janrain Engage single sign on component (gets hung up on the "cross-domain
receiver page," even though all sites including janrain.com, rpxnow.com domains
are allowed).
What steps will reproduce the problem?
1. Go to janrain.com or wishybox.com (both sites that use the Janrain Engage
syndicated login component)
2. Login using OAuth from any of the listed providers (i.e., Google, Windows
Live, Facebook, Twitter, Yahoo!)
3. NotScripts hangs the redirection at the "cross-domain receiver page" (blank
white pop-up page) and doesn't forward on to the proper location. NoScript on
Firefox handles the redirection properly.
4. To prove that NotScripts is at fault, disable the NotScripts extention in
Chrome and observe that the Janrain Engage login works properly and redirects
you to the proper page after successful login.
What is the expected output? What do you see instead?
It is expected that the Janrain Engage login will redirect you to the desired
page when logging in using Janrain Engage single sign on/social login
component. Instead, it gets hung up on the "cross-domain receiver page" and
doesn't forward on to the proper location. (sample URL:
http://login.janrain.com/xdcomm#opener;0:%7B%22redirectUrl%22%3A%22https%3A%5C%2
F%5C%2Flogin.janrain.com%5C%2Fredirect%3Floc%3D6a1da802c83a3270f6f3c162802ef3757
045826f%22%2C%22stat%22%3A%22ok%22%2C%22origin%22%3Anull%7D)
What version of the product are you using? On what operating system?
Version 0.9.6, on Mac OS X 10.6.8.
Please provide any additional information below.
Current Blocking Mode: Whitelist
List Stats
Total # Entries: 2387
Space Occupied (dual-byte encoding): 47969 bytes / 5242880 bytes (0.91494 %)
Est. Space Occupied Encrypted (dual-byte encoding): 153501 bytes / 5242880
bytes (2.92780 %)
Est. Max. Entries: 81528
User Agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.2 (KHTML, like
Gecko) Chrome/15.0.874.106 Safari/535.2
Original issue reported on code.google.com by bhall...@gmail.com on 7 Nov 2011 at 3:41
Original issue reported on code.google.com by
bhall...@gmail.comon 7 Nov 2011 at 3:41