This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 596
Support for Cookie "SameSite" Flag #908
Comments
mariusschulz
changed the title
Support for "SameSite" flag
Support for Cookie "SameSite" Flag
Jul 20, 2016
This was previously discussed here: #831 (comment) SameSite is still in draft form: https://tools.ietf.org/html/draft-west-first-party-cookies-07 We may add support for it when the spec is finished. |
@blowdart has requested this be re-triaged. |
Depends on aspnet/HttpAbstractions#710 |
Need to also make sure we update the Cookie Policy middleware to allow setting this. |
And Security-related cookies from this repo, plus also Antiforgery cookies would have SameSite enabled by default. We'd have to evaluate all other cookies created by ASP.NET Core to see what they should have by default. |
Antiforgery work tracked here: aspnet/Antiforgery#127 |
JunTaoLuo
added
2 - Working
3 - Done
and removed
1 - Ready
2 - Working
needs design
labels
May 19, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Are there any plans to implement support for the cookie
SameSite
flag within the cookie authentication middleware? The flag helps mitigate CSRF attacks and is currently recognized by Chrome and Opera, and possibly more browsers soon.I'm thinking about a new property on
CookieAuthenticationOptions
, as illustrated here:I think this feature has a very good cost-benefit ratio. The implementation should be relatively straightforward, and it wouldn't hurt to have an additional protection measure against CSRF besides antiforgery tokens.
The text was updated successfully, but these errors were encountered: