cookies

Why IdentityServer4 provide/send-back different cookie for each clients?

久未见 提交于 2020-05-17 06:26:10
问题 I have two mvc client application mvc_client1 and mvc_client2 . When I logged into mvc_client1 and click the menu to launch mvc_client2 automatically authenticate and open authorized page as per IdentityServer4 documentation. But, if I trigger logout from any of the client only logout the client which I requested the logout. I have already read documentation and implemented Back-Channel-Logout . Even though single sign-out not working as documented. I noticed something that, Identity server

Set-Cookie header not working across domain

耗尽温柔 提交于 2020-05-15 08:12:30
问题 I am on a website https://aaa.shared.com . This website (call it A ) sends an xhr request to url https://zzz.shared.com/some/path (website Z ) and receives a response with the following headers: access-control-allow-credentials: true access-control-allow-origin: aaa.shared.com set-cookie: foo=bar; expires=Fri, 01 Jan 2100 00:00:00 GMT; path=/; secure; samesite=none; httponly (I followed answer on this question to add access-control headers) Now, what I would expect is that whenever I am on

PHP setting a Session-Cookie with samesite

萝らか妹 提交于 2020-05-15 07:57:05
问题 I currently have a PHP script that sets the sametime cookie as follows: session_set_cookie_params($cookie_timeout, $cookieParams["path"], $cookie_domain, $session_secure, $cookie_httponly); I want to add samesite="Lax" to the above statement by adding an extra parameter where ($cookie_samesite="Lax") session_set_cookie_params($cookie_timeout, $cookieParams["path"], $cookie_domain, $session_secure, $cookie_httponly, $cookie_samesite); The new output of the statement would look like 1800, /, "

How to save cookies [duplicate]

纵饮孤独 提交于 2020-05-14 12:21:37
问题 This question already has answers here : Simple PHP login with cookie (2 answers) Closed 6 years ago . How would I go about having people that say they directly login to my website, How would I make it to where, Once they login they are actually loged in via cookies? To say something like this. "If you would like to actually completely access the website you signup and login, But once you login it saves your cookies, Intill loging out." At the moment, I have the signup and the login but it's

How to persist webview cookies between app executions?

点点圈 提交于 2020-05-14 05:28:12
问题 It is possible to achieve this currently in Android? I only can find deprecated questions about old methods (CookieSynchManager) which not seems to work for this actually. It is possible to achieve it? can't find anything also on the android developers guide. Thank you 回答1: Having the same problem...I solved reading the doc here: https://developer.android.com/reference/android/webkit/CookieSyncManager For future readers: to force the Cookie sync process you can manually call the flush()

How to persist webview cookies between app executions?

夙愿已清 提交于 2020-05-14 05:27:10
问题 It is possible to achieve this currently in Android? I only can find deprecated questions about old methods (CookieSynchManager) which not seems to work for this actually. It is possible to achieve it? can't find anything also on the android developers guide. Thank you 回答1: Having the same problem...I solved reading the doc here: https://developer.android.com/reference/android/webkit/CookieSyncManager For future readers: to force the Cookie sync process you can manually call the flush()

Disable .AspNetCore.Antiforgery Cookie

我的未来我决定 提交于 2020-05-13 08:57:39
问题 Is there any way to prevent the .AspNetCore.Antiforgery Cookie from being created in Asp.Net Core 2? From my understanding services.addmvc internally calls AddAntiforgery and I cannot seem to find any way to prevent this? The reason why this is important is because I cannot set any cookies before the user gives his consent and the .AspNetCore.Antiforgery cookie is set by default. 回答1: OK, I found a solution. If you add this line to ConfigureServices in Startup.cs the cookie will never be

Disable .AspNetCore.Antiforgery Cookie

孤人 提交于 2020-05-13 08:55:05
问题 Is there any way to prevent the .AspNetCore.Antiforgery Cookie from being created in Asp.Net Core 2? From my understanding services.addmvc internally calls AddAntiforgery and I cannot seem to find any way to prevent this? The reason why this is important is because I cannot set any cookies before the user gives his consent and the .AspNetCore.Antiforgery cookie is set by default. 回答1: OK, I found a solution. If you add this line to ConfigureServices in Startup.cs the cookie will never be

Cookie not set with express-session in production

只谈情不闲聊 提交于 2020-05-12 02:53:53
问题 My app is divided between Client and Server. Client is a frontend side Nextjs app hosted on Now.sh, Server is its backend created with Express and hosted on Heroku, so the domains are client-app.now.sh and server-app.herokuapp.com . Authentication Authentication system is based on cookies and I'm using express-session to achieve it. This is my express-session configuration app.use( session({ store: process.env.NODE_ENV === "production" ? new RedisStore({ url: process.env.REDIS_URL }) : new

Cookie not set with express-session in production

巧了我就是萌 提交于 2020-05-12 02:51:11
问题 My app is divided between Client and Server. Client is a frontend side Nextjs app hosted on Now.sh, Server is its backend created with Express and hosted on Heroku, so the domains are client-app.now.sh and server-app.herokuapp.com . Authentication Authentication system is based on cookies and I'm using express-session to achieve it. This is my express-session configuration app.use( session({ store: process.env.NODE_ENV === "production" ? new RedisStore({ url: process.env.REDIS_URL }) : new