No place to implement Claims Enrichment between Authentication and Authorization

[acnicholls-kroll]

When trying to implement a Claims Enrichment middleware, I can see no place to do so, especially when using the new FunctionsApplication from v4

Start by setting up the AspNetCore Integration on the Function Builder

var host = FunctionsApplication.CreateBuilder(args);
host.ConfigureFunctionsWebApplication();

next configure your middleware (which does BOTH AuthN and AuthZ)

host.UseFunctionsAuthorization();

if I add a ClaimsEnrichment middleware BEFORE this, the user is not yet authenticated and I don't have a user identifier.
if I add a ClaimsEnrichment middleware AFTER this, authorization has already taken place and no new claims are added to the user before authorization.

How can I implement my middleware between authN and authZ using DarkLoop v4.2.0? I'm trying to find an extension method or something that lets me register my middleware between AuthN and AuthZ.

[acnicholls-kroll]

basically, when using Isolated, add in a Middleware execution, just here, or separate them into two middlewares and allow developers to control where in the execution pipeline they are, so we can handle claims and custom authZ scenarios better.

[acnicholls-kroll]

see this PR for details: #80

after making local copies of several internal classes, I was able to make this work with the PR'd code.

Let me know if you have any questions.

[artmasa]

Hi @acnicholls-kroll,

This is something it was brought up for another similar scenario and opened #47 to add this.
Thanks for investing the time. I will take a look at your PR this coming week.

I've been thinking what should be the correct approach; if to bring another package for authentication to enable all challenge scenarios possible through authentication in ASP.NET Core. Or just embed an authentication middleware in this authorization package.

[acnicholls-kroll]

Thanks @artmasa, do suggest any changes you think make sense, I wasn't sure about the Middleware method naming conventions as I think it's a breaking change.