Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaking Change: Authentication: AutomaticAuthentication has been split #83

Open
HaoK opened this issue Oct 16, 2015 · 1 comment
Open

Comments

@HaoK
Copy link
Member

HaoK commented Oct 16, 2015

We decided to split the AutomaticAuthentication flag into two new flags to allow controlling the behavior in a more granular way:

AutomaticAuthenticate: determines whether the authentication scheme will call Authenticate and merge any claims principals produced into HttpContext.User

AutomaticChallenge: determines whether the authentication scheme will handle any naked Challenges, i.e. [Authorize], or any explicit challenge calls where the scheme wasn't specified context.Authentication.Challenge()

cc @blowdart @Tratcher

@HaoK HaoK added this to the 1.0.0-rc1 milestone Oct 16, 2015
@aspnet aspnet locked and limited conversation to collaborators Oct 16, 2015
@HaoK
Copy link
Member Author

HaoK commented Oct 16, 2015

To restore similar behavior today:

For cookies, set both AutomaticAuthenticate and AutomaticChallenge to true to mimic the old AutomaticAuthentication: true

For Social Auth, only AutomaticChallenge has any effect since they do not produce principals anyways.

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

1 participant