-
-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8.2.2 - "with the exception of session tokens" is a bit too wide #1091
Comments
I suggest solution one. |
Options:
|
This one is preferred. ... , with the exception of cookie-based session tokens in cookies and token-based session tokens in sessionStorage. |
Link to bleeding edge: 8.2.2
"spin-off" requirement from The Monster Issue #843 (comment)
Current (bleeding edge) solution
v4.0.2-8.2.2
v4.0.2-3.2.3 (deleted from bleeding edge):
For cookie-based sessions there is now separate requirement 3.4.6 in bleeding edge:
Change made for for v4.0.3 (just drop the exception, because for v4.0.3 3.2.3 stays and there is no 3.4.6):
Problem - a bit too wide open exception
Session token IS sensitive piece of information AND it is stored in some browser storage and therefore anyway in conflict with 8.2.2 (without added exception):
With wide-open exception with the exception of session tokens it is allowed to store any type of token in any browser storage.
Solution 1) Should we be more precise with this exception? like (wording needs improvement):
Solution 2) Should we add extra requirement to V3.5.* which says something like:
Then previous 3.2.3 is covered with new 3.4.6 and new 3.5.*
ping @jsulinski
The text was updated successfully, but these errors were encountered: