https://github.com/dazinator/aspnetcore-identity-multidomain
An example trying to get asp.net core identity working with seperate domains
https://github.com/dazinator/aspnetcore-identity-multidomain
Last synced: 4 months ago
JSON representation
An example trying to get asp.net core identity working with seperate domains
- Host: GitHub
- URL: https://github.com/dazinator/aspnetcore-identity-multidomain
- Owner: dazinator
- License: mit
- Created: 2016-09-16T13:12:26.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-09-16T15:41:19.000Z (over 9 years ago)
- Last Synced: 2024-05-22T22:22:30.522Z (about 2 years ago)
- Language: C#
- Size: 537 KB
- Stars: 3
- Watchers: 4
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# AspNetCore-Identity-MultiDomain
An example trying to get asp.net core identity cookie, shared for a domain.
To replicate the problem:
1. On windows, edit your hosts file, adding the following lines, so you will be able to browse the locally running website
on the following domains:
```
127.0.0.1 app.foo.com
127.0.0.1 app.bar.com
127.0.0.1 another.bar.com
```
When you log in, we want the asp.net identity cookie to be shared accross `.bar.com` - so in other words, `.bar.com` and `.foo.com` should be segregated.
To replicate the issue:
2. Start the website running.
3. Browse to `http://app.bar.com:57426/` and register a user account. (It will ask you to apply the EF migrations during this)
4. Once logged in, browse to `http://another.bar.com:57427/` - we want you to still be logged in.
Issue:
Cannot figure out how to segregate the identity cookie for a domain.