类库内配置ClientCredentialsTokenRequest报错，如何保留内部配置解决？

问题场景 #

开发一个采用客户端凭证（client-credentials）认证流程的HTTP客户端类库，计划在类库内部通过PostConfigure配置凭证请求，宿主应用中调用AddAccessTokenManagement。现有代码及问题如下：

类库代码 #

// MY LIBRARY
public static IServiceCollection AddLibraryClient(this IServiceCollection services, Action<LibraryOptions> configureOptions)
{
    services.Configure(configureOptions);

    var options = new LibraryOptions();
    configureOptions(options);
    
    services.PostConfigure<AccessTokenManagementOptions>(opt =>
            {
                if (!opt.Client.Clients.ContainsKey(options.ClientTokenName))
                {
                    opt.Client.Clients.Add(options.ClientTokenName, new IdentityModel.Client.ClientCredentialsTokenRequest
                    {
                        RequestUri = new Uri(options.Authority + "/connect/token"),
                        ClientId = options.ClientId,
                        ClientSecret = options.ClientSecret
                    });
                }
            });
            
            services.AddRefitClient<ILibraryApiClient>()
                .ConfigureHttpClient((_, client) => client.BaseAddress = new Uri(options.Url))
                .AddClientAccessTokenHandler(options.ClientTokenName)
                .AddStandardResilienceHandler();

    return services;
}

宿主应用代码 #

// MY HOST APP
services.AddAccessTokenManagement();
services.AddLibraryClient(options =>
{
    options.Url = "url";
    options.Authority = "authority-url";
    options.ClientId = "client-id"; // 原代码此处缺少闭合引号，需修正
    options.ClientSecret = "client-secret";
    options.ClientTokenName = "token-name";
});

运行时触发错误：

No access token client configuration found for client: my-token-client-name

若在宿主的AddAccessTokenManagement中手动注册令牌客户端，错误会消失，但不符合类库封装的设计要求，需在类库内部完成配置。

解决方案 #

核心问题是原代码提前实例化LibraryOptions，导致PostConfigure使用临时配置而非最终生效配置，同时配置时机未匹配令牌客户端的初始化节奏。修改类库代码如下：

// MY LIBRARY
public static IServiceCollection AddLibraryClient(this IServiceCollection services, Action<LibraryOptions> configureOptions)
{
    // 注册LibraryOptions的配置逻辑
    services.Configure(configureOptions);

    // 使用带IServiceProvider参数的PostConfigure重载，确保获取最终配置
    services.PostConfigure<AccessTokenManagementOptions>((tokenOptions, serviceProvider) =>
    {
        var libraryOptions = serviceProvider.GetRequiredService<IOptions<LibraryOptions>>().Value;
        
        if (!tokenOptions.Client.Clients.ContainsKey(libraryOptions.ClientTokenName))
        {
            tokenOptions.Client.Clients.Add(libraryOptions.ClientTokenName, new IdentityModel.Client.ClientCredentialsTokenRequest
            {
                RequestUri = new Uri($"{libraryOptions.Authority}/connect/token"),
                ClientId = libraryOptions.ClientId,
                ClientSecret = libraryOptions.ClientSecret
            });
        }
    });
    
    services.AddRefitClient<ILibraryApiClient>()
        .ConfigureHttpClient((serviceProvider, client) =>
        {
            // 从服务提供者获取最终配置
            var libraryOptions = serviceProvider.GetRequiredService<IOptions<LibraryOptions>>().Value;
            client.BaseAddress = new Uri(libraryOptions.Url);
        })
        .AddClientAccessTokenHandler(serviceProvider =>
        {
            // 动态获取令牌客户端名称
            var libraryOptions = serviceProvider.GetRequiredService<IOptions<LibraryOptions>>().Value;
            return libraryOptions.ClientTokenName;
        })
        .AddStandardResilienceHandler();

    return services;
}

关键修改点 #

• 延迟获取配置：不再提前实例化LibraryOptions，而是在PostConfigure、ConfigureHttpClient和AddClientAccessTokenHandler中通过IServiceProvider获取IOptions<LibraryOptions>的最终值，确保配置是宿主所有配置逻辑执行后的结果。
• PostConfigure依赖注入：使用接受IServiceProvider的PostConfigure重载，保证处理AccessTokenManagementOptions时，LibraryOptions已完成所有配置。
• 动态令牌客户端名称：在AddClientAccessTokenHandler中动态获取令牌名称，避免提前绑定导致的配置不一致。

额外注意 #

宿主应用代码中存在语法错误：options.ClientId = "client-id; 缺少闭合引号，需修正为options.ClientId = "client-id";，否则会导致配置失败。

内容的提问来源于stack exchange，提问作者Duc Thang