# Okta Authentication using http (not https) in a webforms .net web application **URL:** \ **Category:** OAuth/OIDC\ **Created:** [October 31, 2022, 12:39am UTC](https://devforum.okta.com/t/okta-authentication-using-http-not-https-in-a-webforms-net-web-application/22292 "2022-10-31T00:39:05Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![warren](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@warren](https://devforum.okta.com/u/warren)\ **Post date:** [October 31, 2022, 8:47pm UTC](https://devforum.okta.com/t/okta-authentication-using-http-not-https-in-a-webforms-net-web-application/22292/2 "2022-10-31T20:47:07Z")
You can try out this sample app [GitHub - oktadev/okta-aspnet-webforms-example: An example of how to integrate Okta for authentication in an ASP.NET Webforms application.](https://github.com/oktadev/okta-aspnet-webforms-example) However, I believe the change to use HTTPS is due to the SameSite cookie changes back in 2020. [https://support.okta.com/help/s/article/FAQ-How-Chrome-80-Update-for-SameSite-by-default-Potentially-Impacts-Your-Okta-Environment](https://support.okta.com/help/s/article/FAQ-How-Chrome-80-Update-for-SameSite-by-default-Potentially-Impacts-Your-Okta-Environment) You can refer to this post as well. > [@Okta.AspNet SameSite issue](https://devforum.okta.com/t/okta-aspnet-samesite-issue/7762/4): > > 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… --- _[View the full topic](https://devforum.okta.com/t/okta-authentication-using-http-not-https-in-a-webforms-net-web-application/22292)._