You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2018. It is now read-only.
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.
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
The text was updated successfully, but these errors were encountered: