Cfrgtkky

I have this in my startup:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)

{

    if (env.IsDevelopment())

    {

        app.UseDeveloperExceptionPage();

    }

    else

    {

        app.UseHsts();

    }



    app.UseHttpsRedirection();

    app.UseStaticFiles();

    app.UseSwaggerWithUi();



    app.UseAuthentication();

    app.UseMiddleware<SomeMiddleware>();



    app.UseMvc();

}

I need to add some additional claims AFTER the user is authenticated, but the middleware Invoke function always fires before Auth (HttpContext.User.Identity.IsAuthenticated is false). But when it hits the controller the user is authenticated fine.

Any idea what to do here? I've tried to put "app.UseAuthentication()" after calling app.UseMiddleware but it has no affect.

I'm currently using multiple Authentication schemes. I'm not sure if that has an affect.

You can add another middleware immediately after the UseAuthentication() to add claims :

app.UseAuthentication();

app.Use(async(context, next)=>{

    if(context.User !=null && context.User.Identity.IsAuthenticated){

        // add claims here 

        context.User.Claims.Append(new Claim("type-x","value-x"));

    }

    await next();

});



//  call other middlewares 

app.UseMiddleware<SomeMiddleware>();

It depends on what do you want to do and which scheme you use.

For example, if you use JwtBearer then you could utilize JwtBearerOptions.Events to handle particular events raised by the middleware. You need to set that in your ConfigureServices method of Startup class.

That would give you more granular control of what precise case you want to have your Claims added to, for example, OnTokenValidated.