C#•2y ago

✅ Authentication with Cookies

I'm playing around with cookies to get a better understanding. My code:

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddAuthentication("cookie")
    .AddCookie("local");

var app = builder.Build();

app.UseAuthentication();

app.MapGet("/", () => "Hello World!");

app.MapGet("/login", async (HttpContext ctx) =>
{
    var claims = new List<Claim>();
    claims.Add(new Claim("usr", "daniel"));
    var identity = new ClaimsIdentity(claims, "local");
    var user = new ClaimsPrincipal(identity);
    await ctx.SignInAsync("local", user);
});

app.MapGet("/user-info", (HttpContext ctx) =>
{
    return ctx.User.FindFirstValue("usr") ?? "empty";
});

app.Run();

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddAuthentication("cookie")
    .AddCookie("local");

var app = builder.Build();

app.UseAuthentication();

app.MapGet("/", () => "Hello World!");

app.MapGet("/login", async (HttpContext ctx) =>
{
    var claims = new List<Claim>();
    claims.Add(new Claim("usr", "daniel"));
    var identity = new ClaimsIdentity(claims, "local");
    var user = new ClaimsPrincipal(identity);
    await ctx.SignInAsync("local", user);
});

app.MapGet("/user-info", (HttpContext ctx) =>
{
    return ctx.User.FindFirstValue("usr") ?? "empty";
});

app.Run();

Currently, the user-info endpoint returns "empty" after getting a cookie from the login endpoint. When I changed to AddCookie("cookie"), and change the ClaimsIdentity and Signin to "cookie", it returns a claim value. I was under the impression I could name the AddCookie scheme whatever I would like. Could someone please explain?

10 Replies

Unknown User•2y ago

Message Not Public

sonodan.•2y ago

Yep, a cookie called .AspNetCore.local

Unknown User•2y ago

Message Not Public

sonodan.•2y ago

Hmmm no the ctx.User.Claims doesn't contain any claims. When I switch "local" for "cookie" in all places, it adds the claim

Unknown User•2y ago

Message Not Public

Pobiega•2y ago

Isnt that expected? SignInAsync doesnt take the cookie name, it takes the login auth schema which is "cookie" here

sonodan.•2y ago

I tried this, but get this exception

Pobiega•2y ago

https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection.authenticationservicecollectionextensions.addauthentication?view=aspnetcore-7.0#microsoft-extensions-dependencyinjection-authenticationservicecollectionextensions-addauthentication(microsoft-extensions-dependencyinjection-iservicecollection-system-string) in the code block you pasted above, you are adding "cookie" as your fallback signin schema, then adding a new cookie schema called "local"

sonodan.•2y ago

ah it seems I was misunderstanding. I thought the fallback signin schema meant the type of schema, for instance cookie or JWT. I didn't realize it had to match one of the names of the schemas adding, i thought it meant the type thank you both!

Accord•2y ago

Closed!

Gaming

Programming

✅ Authentication with Cookies