[RESOLVED] NoScript impeding Pearson myeconlab

[Your script sucks!]

Hello:

My macroeconomics professor uses pearson.com's "myeconlab" for assignments and tests. The login and portal address is domain "pearsoncmg.com" and the actual online course is domain "openvelum.ecollege.com."

Initially, I was able to log in to Pearson's portal and view my courses, but once I selected my macroeconomics course (Pearson calls it "myeconlab"), I would wind up back at the portal log in page. It was a never ending loop.

I next isolated NoScript as the culprit addon. Now I need to find out which NoScript feature is the culprit. Here's what I tried so far:
1. Whitelisted all sites involved and checked for needed sites in the Untrusted list
2. Globally enabled scripts
3. Disabled ABE
4. Disabled ClearClick for both trusted and untrusted sites
5. Disabled both the sanitize and post-to-get options under XSS tab.
6. Went for a walk

I don't mind troubleshooting the issue myself. In fact, I need the practice. But I'm not sure what direction I should take to proceed from this point. Help? Help!

[therube]

Any change if you clear cookies?

Anything [NoScript] related in Error Console?

[Thrawn]

Landing back at the login page sounds like it could be a problem with automatic secure cookie management. (Or, more accurately, a problem with a poorly-designed site, which breaks when cookies are managed securely.)

As therube said, look for NoScript-related messages in the Browser Console.

[Your script sucks!]

Hello, and thank you for your timely responses. And I'm sorry for the lack of mine.

The source of the problem was indeed the Automatic Secure Cookies Management! I forgot that was a NoScript feature, and I felt kinda stupid, so thank you very much for squaring me away!

Now here is the minimum I have to whitelist in order to make everything work.

JS Whitelist:
ecollege.com
mypearson.com
pearsoncmg.com
pearsoned.com

ASCM Whitelist:
*.pearsoncmg.com
*.ecollege.com

And I might be able to be more specific than that by using "openvellum.ecollege.com". Also, portal.mypearson.com had quite a few certificate errors for using SHA-1, and Firefox linked said errors to this site.

Again, thank you very much for helping me out with this. You all are much appreciated!

[Thrawn]

Hello, and thank you for your timely responses. And I'm sorry for the lack of mine.

Taking a day to respond is absolutely fine. Besides, even if you took longer, it doesn't affect us much.

The source of the problem was indeed the Automatic Secure Cookies Management! I forgot that was a NoScript feature, and I felt kinda stupid, so thank you very much for squaring me away!

You shouldn't feel stupid for forgetting about a feature that doesn't trigger anything visible outside the Browser Console. Or any other feature, really.

Glad to hear that sorted it out.

Also, portal.mypearson.com had quite a few certificate errors for using SHA-1

Yeah, SHA-1 signatures are deprecated and going away gradually, but they still work for now. Nothing to do with NoScript, anyway.

Again, thank you very much for helping me out with this. You all are much appreciated!

You're welcome . I'll mark the topic as resolved.