# Okta.AspNet SameSite issue

**URL:** <https://devforum.okta.com/t/okta-aspnet-samesite-issue/7762>\
**Category:** Questions\
**Created:** [January 23, 2020, 11:11am UTC](https://devforum.okta.com/t/okta-aspnet-samesite-issue/7762 "2020-01-23T11:11:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gpadma](https://avatars.discourse-cdn.com/v4/letter/g/858c86/32.png) [@gpadma](https://devforum.okta.com/u/gpadma)\
**Post date:** [November 6, 2020, 7:57am UTC](https://devforum.okta.com/t/okta-aspnet-samesite-issue/7762/4 "2020-11-06T07:57:55Z")

</div>

Hi @marcin @jharris,  
I would like to add this is caused by the new security implementation launched in version 80.

If enabled, cookies without SameSite restrictions must also be Secure. If a cookie without SameSite restrictions is set without the Secure attribute, it will be rejected.

For the cookies to be set with ‘secure’ attribute, you have to make sure the communication is https and not http. I suggest you to check the configuration in your application and environment(proxy, load balancer…) to make sure the protocol is https.

You can however disable (may not be recommended) this in chrome://flags but it is now enabled by default

#cookies-without-same-site-must-be-secure

You’ll have to restart chrome once you’ve set this to disabled.

---

_[View the full topic](https://devforum.okta.com/t/okta-aspnet-samesite-issue/7762)._