huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
aspnetcore/samples/VirtualSchemes.PathSchemeSe...
History
Hao Kung 0686383c90 Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
..
Controllers Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
Models Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
Views Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
wwwroot Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
.bowerrc Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
Program.cs Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
README.md Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
Startup.cs Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
VirtualSchemes.PathSchemeSelection.csproj Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
appsettings.Development.json Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
appsettings.json Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
bower.json Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00
bundleconfig.json Add PathSchemeSelection sample 2017-12-12 15:14:54 -08:00

README.md

AuthSamples.VirtualScheme.PathSchemeSelection

Sample demonstrating selecting between cookie and another authentication scheme based on the request:

Cookie flow is the same, but notice in Startup how the "Request" virtual scheme is now the default scheme

  1. Run the app and click on the MyClaims tab, this should trigger a redirect to login.
  2. Login with any username and password, the sample just validates that any values are provided.
  3. You should be redirected back to /Home/MyClaims which will output a few user claims from the cookie
  4. Now try going to /api/Home/MyClaims which will output a different set of claims (from the Api scheme)

Startup.cs is the most interesting class in the sample.