在 Startup.cs 之外更新 asp.net 核心身份验证

Question

With respect to asp.net core identity management, we have a requirement to change the Microsoft ClientId and ClientSecret after our asp.net core app has started and, therefore, not in startup.cs. We have various identity management logins working fine with, for example this for Microsoft Azure:

            .AddMicrosoftAccount(microsoftOptions =>
            {
                microsoftOptions.CorrelationCookie.HttpOnly = true;
                microsoftOptions.CorrelationCookie.SecurePolicy = CookieSecurePolicy.Always;
                microsoftOptions.ClientId = "removed";
                microsoftOptions.ClientSecret = "removed";
            })

We now need to change the ClientId and ClientSecret dynamically after the core application has started and what we can't figure out is how to access this from the services collection later in other pages so we can update them.

Any help appreciated.

Thanks.

Answer 1

ASP.NET Core provides IAuthenticationSchemeProvider interface to dynamically add/remove authentication schemes at runtime. You can inject this interface and add Microsoft Account auth schemes after the app has started.

Using Microsoft's demo app as reference, here's a basic implementation:

public class DynamicAuthController: ControllerBase
{
    private IAuthenticationSchemeProvider _schemeProvider;
    private IOptionsMonitorCache<MicrosoftAccountOptions> _optionsCache;

    public DynamicAuthController(IAuthenticationSchemeProvider schemeProvider, IOptionsMonitorCache<MicrosoftAccountOptions> optionsCache)
    {
        _schemeProvider = schemeProvider;
        _optionsCache = optionsCache;
    }

    [HttpPost]
    public ActionResult Add()
    {
        var schemeName = "MicrosoftCustom1"; // must be unique for different schemes
        var schemeOptions = new MicrosoftAccountOptions
        {
            ClientId = "ididid", // fetch credentials from another service or database
            ClientSecret = "secretsecret",
            CorrelationCookie =
            {
                HttpOnly = true,
                SecurePolicy = CookieSecurePolicy.Always
            }
        };
        
        var scheme = new AuthenticationScheme(schemeName, displayName:null, typeof(MicrosoftAccountHandler));
        _schemeProvider.TryAddScheme(scheme);
        _optionsCache.TryAdd(
            schemeName,
            schemeOptions
        );

        return Ok();
    }
}