-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Binding Secure cookies to ITlsTokenBindingFeature #4680
Comments
On a related note, you should also consider adding an option in the cookies middleware to disable this feature as it may prevent sharing cookies with OWIN/Katana apps using the interop stuff. |
I'd prefer to enable/disable ITlsTokenBindingFeature at the source (e.g. the server) rather than at each consumption point. |
Well, I guess we could argue that one may want to disable it for a specific cookie only, rather than for the entire app, but either way, I'm fine. |
Need to follow up with partner teams for ANCM and SslStream to see their plans for RTM. We could theoretically start implementing this here and test with WebListener, but only once we have commitment from partners. |
Moving to backlog because it is unclear when we would bring this in. |
Closing as it's unlikely token binding is alive any more. |
Any protected cookie marked as Secure should also use ITlsTokenBindingFeature as part of its protection.
Today CookieAuth always uses ITlsTokenBindingFeature if it's available, ignoring CookieSecureOption. Check CookieSecureOption before applying ITlsTokenBindingFeature.
Other protected data to consider:
OAuth state field
OIDC state fields
OIDC nonce
Twitter request token
The text was updated successfully, but these errors were encountered: