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

Integrate Microsoft.Owin.Security #1667

Merged
merged 18 commits into from
Oct 22, 2013
Merged

Integrate Microsoft.Owin.Security #1667

merged 18 commits into from
Oct 22, 2013

Conversation

analogrelay
Copy link
Contributor

Fixes #1659

This just integrates Microsoft.Owin.Security in to existing username/password and API key auth to prep for OAuth.

Test Notes

  • Create some SHA1-password users before deployment (I'll send out instructions)
  • Log in with various users having PBKDF2 ("new") and SHA1 ("old") passwords, verify that SHA1 passwords are replaced (instructions to come)
  • Log off and try to directly hit a URL like "/account", verify redirect to login page and redirect back to "/account" after login
  • Upload packages through the GUI
  • Upload packages through NuGet push API
  • Use NuGet push with no API Key -> Get Username prompt
  • Use NuGet push with bogus API Key -> Get Forbidden response
  • Use NuGet push with API key that doesn't own package -> Get Forbidden response
  • Log in, then navigate to "http://[nuget site root]/" -> Redirects to SSL Homepage
  • Log off, verify that the following Cookies are NOT present: ".AspNet.Cookies", ".ForceSSL"

@analogrelay analogrelay merged commit 27a8a4d into dev Oct 22, 2013
@analogrelay analogrelay deleted the anurse/1659-owinsecurity branch December 9, 2013 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant