InformAction Forums

The Adobe page to create an acct (link on signin page "Don't have an Adobe ID") or page to sign in , once have an acct, require clicking "Allow All on this page," reloading the page, clicking again "Allow all / all on this page," reloading page... multiple times https://www.adobe.com/account/sign-in.forums.htm.

Even then, it's iffy in Fx 28 whether it'll take the user / PW & log me in. Everything else besides NS is disabled on Adobe pages.

Yesterday, was finally able to login. Had to "allow all on this page" several times & enable scripts globally before could create an acct., or signin. Today, can't login. Today on signin page above, there are no entries today on NS menu showing "Allow or temporarily allow...". Everything on NS menu is "Mark <site> as Untrusted."
Scripts are globally enabled. Cookies enabled. Still can't get past sign in page, but was successful at least 2x yesterday. IE 9 logs in immediately - but I use it as last resort or for testing.

Unless I missed the secret, easy trick for this site (possible), NS makes it nearly impossible / very tedious to register / login. Technically, there's not (a single) "disable NS on this site" selection but maybe should be.

Other security / privacy addons have it. This site is another example how on some sites, NS makes them almost inaccessible or the required steps to use the site / login become prohibitive for many users. I will pursue it, but a good many would just disable NS completely.

When login fails, anything related in the Browser Console? (Ctrl-Shift-J)

A lot in browser console - probably too much for me to sort thru & find anything preventing login.

I discovered that not allowing network.http.sendRefererHeader to send header (value set = 0), was also preventing login. I still had to whitelist adobe.com & adobetag.com in NS, but changing sendRefererHeader to "2" allowed not having to enable scripts globally in NS.

For me, it's rare that having sendRefererHeader set = 0 affects anything on sites - even financial, gov't, etc.
Still, the Adobe site is pretty convoluted. Has an amazing # of scripts, 3rd party sites.

Question: I'm not sure how / why NS seems to store temporary allowances... after closing adobe site, clearing their cookies, clearing my cache, or even after closing Fx & "clearing All private data" before closing it. NS still seems to show multiple addresses as still allowed, though they weren't necessarily in the whitelist (i.e., NS menu would show selections to "forbid <various adobe sites>"). As said, that was when adobe.com & several others appearing in NS menu, were NOT whitelisted.

So if they were given temporary permission, why were the sites still allowed in NS, after closing the site, clearing cache & even restarting Fx (clearing all private data, in the process)?
After the clearing / closing Fx process, couple of times when I saw adobe & certain related sites were still allowed (which may be required on this site, but...), I looked in NS whitelist & the sites weren't there.

How is NS seemingly preserving temporary allowances between sessions or after closing a site / tab?
Thanks.

You clear NoScript "temps" with 'Revoke Temporary Permissions', either from the icon, or from within Options.

scripteze wrote:A lot in browser console - probably too much for me to sort thru & find anything preventing login.

Usually, NoScript-related messages start with "[NoScript" or "[ABE]".

scripteze wrote:Question: I'm not sure how / why NS seems to store temporary allowances...
(snip)
or even after closing Fx & "clearing All private data" before closing it. NS still seems to show multiple addresses as still allowed, though they weren't necessarily in the whitelist (i.e., NS menu would show selections to "forbid <various adobe sites>"). As said, that was when adobe.com & several others appearing in NS menu, were NOT whitelisted.

So if they were given temporary permission, why were the sites still allowed in NS, after closing the site, clearing cache & even restarting Fx (clearing all private data, in the process)?
After the clearing / closing Fx process, couple of times when I saw adobe & certain related sites were still allowed (which may be required on this site, but...), I looked in NS whitelist & the sites weren't there.

How is NS seemingly preserving temporary allowances between sessions or after closing a site / tab?
Thanks.

Temporary permissions are not supposed to persist after browser restart, but I know you're not the first to see this. Can't find those threads now though.

OK. I see that - "revoke temporary permissions." I was thinking of "temporary" as not requiring specific user action, esp. after deleting all private data & closing the browser. At least, that's the way most addons I'm familiar with work. Temporary in addons usually means the settings or allowed action (allowing cookies, etc.) are reset to default on closing Fx.

The NS features / help page http://noscript.net/features, says:

The "Temporarily" permissions are in effect until you exit the browser.

I'm not finding that's true. Do all instances of "temporarily allow this <site>, <page>" revert / disappear for you, when Fx is closed? If so, something's wrong w/ my install of NS. If not, then either there's a bug or the features descrip. of this is wrong?

This question isn't related to NS per se, but what kind of data might appear in browser / web console (under which tab), that indicates a page isn't working because of sendRefererHeader being changed from default (default allows sending the full header)? For me, it affects pages so rarely, I probably don't immediately think of it as potential cause. 99.9% of problems are caused by something being blocked by AB+, Ghostery or NS.

Temporary permissions do disappear on browser exit for me.
I did find the other threads on that issue, but they're not helpful. You'll probably need to do Standard Diagnostic to isolate the cause. Please let us know the results, thanks.

I used a clean profile & installed latest NS. Temp permissions seem to be cleared now, when Fx is closed - but not simply by closing the tabs of sites visited in current session, if anyone's expecting that to happen. I'm fairly sure that's how NS is designed.
***********************
EDIT: 3/27_ Then I uninstalled / reinstalled NS in my daily profile. That seemed to fix the problem of it not deleting temp permissions after closing Fx. Reinstalling extensions having problems back in same profile often doesn't fix issues - so I sneaked by on this one.
**********************

Much the same as "session cookies" are deleted by some cookie handlers, when the browser's closed, but not when simply close tabs.

Otherwise, I guess you'd have to manually click "Revoke temporary permissions," in NS menu or options UI.

That said, other than uninstalling NS & reinstalling (in current profile), it's fairly tedious finding the cause of such glitches.

Like many, I get tired of frequently having to troubleshoot extensions for conflicts w/ others, or w/ Fx. In 4+ yrs, I've never had to reinstall Windows on this box. It's had several orders of magnitude more things installed in it than Fx / any Fx profile, etc., ever will. Firefox and /or it's profiles seem to get corrupted far more than anything I've ever used. And I use fewer extensions than most.

Did you find anything in the Browser Console?

If needed, you can just save the whole thing and send it to a moderator via private message (I'm pretty sure the spam filter won't let you post it).

scripteze wrote:Technically, there's not (a single) "disable NS on this site" selection but maybe should be.

Other security / privacy addons have it.

Privacy, yes, eg Adblock Plus. But which security addons are you referring to?

Thanks to all for the info.
I found very little related to NS on the Adobe site, if I was looking in the right place. That's not to say I didn't miss some entries. But, there'll be a next time & the info will be useful.
Is there one particular tab where NS entries would show up? Only thing I saw was these lines & I don't think they're bothering anything:

reflow: 0ms function <anonymous>, noscriptOverlay.js line 1552
reflow: 0ms function <anonymous>, noscriptOverlay.js line 1552

Adobe's forums (& site in general) have a lot of their own subdomains & true 3rd parties trying to load scripts, to be sure.
They're not all required to login. In this case, I think the sticking point was "referer header" being set = 0 in Fx (send no header). As soon as I changed that, the adobe site worked.

Adobe requires referer header to be set = 2 to login (send full header data). Setting it at 1 isn't good enough.

Send Referer header being turned off very rarely causes me any problems (almost never). I've had it set to 0 forever & never had problems w/ banks, forums (before now) - not even youtube - run by world's greatest info gatherer. That's why I didn't suspect it sooner, or even think about it.

You can use RefControl to send referrer header to Adobe while still hiding for other sites.