@Pier56
Something is gumming up the works, and I do not know where it is, so one possible fix - if only temporary for testing - is to thoroughly remove possible stumbling blocks.
In a Brave Browser New Window, go to: brave://settings/clearBrowserData
- For
Time range > All time, using the Basic tab
- Enable
Cookies and other site data
- Enable
Cached images and files
- Click the
Delete data button
Exit / Quit everything. Restart the computer. Start up Brave Browser
Using a Brave Browser New Window (not a private window, from here on), visit the Newspaper’s webpage and click on its “Sign On” button.
In general terms, at the Newspaper’s sign-on webpage, the URL address might be something like:
https://accounts.newspaper.com ← the hostname is accounts.newspaper.comhttps://login.newspaper.com ← the hostname is login.newspaper.com
For the following steps, let us say that hostname is login.newspaper.com - OF COURSE, you would be substituting your actual Newspaper’s domain name.
A) In a Brave Browser New Window, go to each of the following Brave Browser site details settings windows and click the Reset permissions button for:
brave://settings/content/siteDetails?site=https%3A%2F%2Flogin.newspaper.combrave://settings/content/siteDetails?site=https%3A%2F%2Fwww.newspaper.combrave://settings/content/siteDetails?site=https%3A%2F%2Fnewspaper.com
B) In a Brave Browser New Window, go to: brave://settings/content/braveShields and, in the Shields Down section, Add, one-at-a-time:
login.newspaper.comwww.newspaper.comnewspaper.com
C) In a Brave Browser New Window, go to: brave://settings/cookies and, in the Sites allowed to use third-party cookies section, Add, one-at-a-time:
login.newspaper.comwww.newspaper.comnewspaper.com
D) In a Brave Browser New Window, go to: brave://settings/content/javascript and scroll down to the Allowed to use JavaScript section. There, Add: [*.]newspaper.com but DO NOT Enable the Current Private session only checkbox.
Stay on that settings page and repeat those steps to allow JavaScript sources, for:
[*.]login.newspaper.com[*.]www.newspaper.com
Exit / Quit Brave Browser. Pause a few seconds. Start up Brave Browser. Test your issue.
Please understand, that the above procedures ALLOW the website to be treated as if it has Most Trusted status.
Why (A): For future references, handy to know the brave://settings/content/siteDetails?site=https%3A%2F%2F portion of each of those, is a fixture followed by either a domain name or hostname. The reason I favor this un-conventional method on some occasions, is for situations when/where there is a domain name or hostname that is involved, but you cannot visit its https://... URL address with the browser, and therefore you are unable to follow the procedure where you “click the ‘tune’ icon”. The Microsoft eco-system has several such domain names, hostnames. Google eco-system and Yahoo/AOL eco-system have them, too.
Why (B): Ensures that Site-Specific Brave Shields are DOWN regardless of events that may redirect/reload the webpage(s)/website.
Why (C): Satisfies cross-site tracking that more and more “eco-systems” of “unified logins” (like Google → accounts.google.com) require for better reliability/stability regarding their identifying “you” (your online behavior, software, hardware ← ID, fingerprints, etc.). Ensures that cookies persist (if necessary/required by the website) for events that may redirect/reload the webpage(s)/website.
Why (D): Ensures that JavaScript sources from specific sites, will be Allowed; and that Allowance persists, again, for events that may redirect/reload the webpage(s)/website.
Why Overall?: Because websites are now more fussy about their persistant access to (they hope) persistant ID information about you/“you.”