Add service for storage of tokens in auth properties

[josephdecock]

This is pretty complex logic, because we can have per-scheme and/or per-resource tokens, and we need to store additional metadata as well. By exposing this as a service, we can reuse the logic elsewhere (I needed it in the BFF to use its session store as a token store).

[brockallen]

Only review question: service interface or extension methods?

[josephdecock]

I don't have a strong opinion on service vs extension method.

Pro/con of service:
Con: Service suggests an extensibility point where none is intended
Pro: Service might be easier to mock

[brockallen]

Con: Service suggests an extensibility point where none is intended

Right... this was the main thing I was worried about. Also con, if the implementation needs more stuff from DI (e.g. logger) then it makes more sense as a service.

Anyway, your call.

[josephdecock]

We do have a lot of dependencies, so I'm leaning away from extension methods actually:

    IOptions<UserTokenManagementOptions> tokenManagementOptions, // TODO - Consider option lifetime
    IAuthenticationSchemeProvider schemeProvider,
    ILogger<StoreTokensInAuthenticationProperties> logger,
    IOptionsMonitor<CookieAuthenticationOptions> cookieOptionsMonitor