Skip to content
This repository has been archived by the owner on Dec 20, 2018. It is now read-only.

Cookie names not set properly. #763

Closed
JunTaoLuo opened this issue Mar 7, 2016 · 2 comments
Closed

Cookie names not set properly. #763

JunTaoLuo opened this issue Mar 7, 2016 · 2 comments
Assignees
Milestone

Comments

@JunTaoLuo
Copy link
Contributor

I overlooked the fact that setting the AuthenticationScheme values does not actually achieve what we want. By default, schemes are set to .AspNetCore.{AuthenticationScheme} and this leads to names like .AspNetCore..AspNetCore.Identity.Application since cookies middleware adds the .AspNetCore. prefix by default. We can remove the .AspNetCore. from the prefix of the authentication scheme.

Still investigating the why there are also cookies like .AspNetCore.Microsoft.AspNetCore.Identity.ExternalLogin.

Edit: Ignore the ExternalLogin cookie issue. That is a really old legacy name for the cookie and the test is only checking it for non-existence.

fyi @natemcmaster

@natemcmaster
Copy link
Contributor

By default, cookie names are set to .AspNetCore.{AuthenticationScheme}

Where is this in code?

@JunTaoLuo
Copy link
Contributor Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants