Visiting: https://store.playstation.com/ Won't allow user to login.
https://store.playstation.com/ Login will fail.
Expect menus and login to work.
Easily
Version 1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Version 1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Allow Cookies in shields is needed
Affecting at least 3 sony domains I'm are of: It seems we need to allow cookies on all 3 domains.
https://my.playstation.com/ (redirects to id.sonyentertainmentnetwork.com)

During the login process for playstation.com (where its failing), The site will re-direct from playstation.com to sonyentertainmentnetwork.com . We needed to allow cookies on both domains to make Brave workable
Looking at the logs:
On the domain: playstation.com
We should allow cookies from: sonyentertainmentnetwork.com
And in reverse;
On the domain sonyentertainmentnetwork.com
Allow cookies from playstation.com
@pes10k thoughts?
I believe this will be solved by the PR coming from https://github.com/brave/brave-core/tree/fix-google-drive-autoplay-bj, very shortly (likely w/in the next 24 hours)
Verified on
Brave | 1.9.76 Chromium: 81.0.4044.138聽(Official Build)聽(64-bit)
-- | --
Revision | 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999}
OS | Windows聽10 OS Version 1803 (Build 17134.1006)
Important: Account creation is allowing to sign in the website, but the clean profile is not allowing to login with existing login credentials
Note: Sign In option on the PlayStation website is shown only after enabling All cookies allowed

Still able to reproduce the issue of not being able to login.
Login button on store.playstation.com - this is mentioned in Miscellaneous Information section of https://github.com/brave/brave-browser/issues/8629#issue-579058593, so maybe this is ok.
Steps used:
Brave | 1.9.76 Chromium: 81.0.4044.138聽(Official Build)聽(64-bit)
-- | --
Revision | 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999}
OS | macOS Version 10.14.6 (Build 18G3020)
cc @rebron @bsclifton @pes10k
Per discussion, marking as release-notes/exclude and QA/No as issue still reproduces. Logged follow up issue for this to be addressed: https://github.com/brave/brave-browser/issues/9987.