Contents
Cookie authentication uses HTTP cookies to authenticate client requests and maintain session information. The client sends a login request to the server. On the successful login, the server response includes the Set-Cookie header that contains the cookie name, value, expiry time and some other info.
Setting cookies for another domain is not possible. If you want to pass data to another domain, you can encode this into the url.
Is there such thing as cross domain cookies?
That’s how they recognize you on cnn.com and display your friends there. There’s no such thing as cross domain cookies. You could share a cookie between foo.example.com and bar.example.com but never between example.com and example2.com and that’s for security reasons. You cannot share cookies across domains.
A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. So if your backend server does not set SameSite=None, Chrome will use SameSite=Lax by default and will not use this cookie with { withCredentials: true } requests.
Websites often consist of individual web apps working together. To provide a single sign-on (SSO) experience, web apps within a site must share authentication cookies. To support this scenario, the data protection stack allows sharing Katana cookie authentication and ASP.NET Core cookie authentication tickets.
Can you share cookies in a single domain?
As other people say, you cannot share cookies, but you could do something like this: centralize all cookies in a single domain, let’s say cookiemaker.com. when the user makes a request to example.com you redirect him to cookiemaker.com. cookiemaker.com redirects him back to example.com with the information you need.