刷新JWT令牌是否需每次新建gRPC Channel？

你当前的实现是在创建GrpcChannel时把JWT令牌硬编码到CallCredentials拦截器中，导致令牌固定无法更新——实际上完全不需要为了更新令牌重建Channel，只需要调整令牌的获取逻辑，让拦截器每次调用时动态读取最新的令牌即可。

你的原始代码：

private GrpcChannel GetCanal(string paramStrDireccion, int paramIntPuerto, string? paramStrTokenJwt = null)
{
    SocketsHttpHandler miHttpHandler = new SocketsHttpHandler();
    miHttpHandler.SslOptions.RemoteCertificateValidationCallback = ValidateServerCertificate;

    HttpClient httpClient = new HttpClient(miHttpHandler);

    GrpcChannelOptions misOpcionesDelCanal = new GrpcChannelOptions()
    {
        MaxReceiveMessageSize = 62914560,
        MaxSendMessageSize = 62914560,
        HttpClient = httpClient,
    };

    if (string.IsNullOrWhiteSpace(paramStrTokenJwt) == false)
    {
        CallCredentials misCredenciales = CallCredentials.FromInterceptor((c, m) =>
        {
            m.Add(HeaderNames.Authorization, $"Bearer {paramStrTokenJwt}");
            return Task.CompletedTask;
        });

        misOpcionesDelCanal.Credentials = ChannelCredentials.Create(new SslCredentials(), misCredenciales);
    }

    try
    {
        Uri miUri = new Uri(paramStrDireccion + ":" + paramIntPuerto.ToString());
        GrpcChannel miCanal = GrpcChannel.ForAddress(miUri, misOpcionesDelCanal);
        return miCanal;
    }
    catch
    {
        throw new ArgumentException("The data of the server aren't correct.");
    }
}

修改方案：动态获取最新令牌 #

调整核心思路：将JWT令牌存储为可更新的类级变量，让CallCredentials拦截器每次处理调用请求时读取最新值，而非捕获创建时的固定参数。

示例代码：

// 类级变量存储服务器信息、复用的Channel和当前JWT
private readonly string _serverAddress;
private readonly int _serverPort;
private readonly GrpcChannel _grpcChannel;
private string? _currentJwtToken;
// 线程安全锁，保证令牌更新和读取的原子性
private readonly object _tokenLock = new object();

// 初始化方法：只创建一次Channel
public YourGrpcClientWrapper(string serverAddress, int serverPort)
{
    _serverAddress = serverAddress;
    _serverPort = serverPort;
    _grpcChannel = InitializeChannel();
}

private GrpcChannel InitializeChannel()
{
    SocketsHttpHandler miHttpHandler = new SocketsHttpHandler();
    miHttpHandler.SslOptions.RemoteCertificateValidationCallback = ValidateServerCertificate;

    HttpClient httpClient = new HttpClient(miHttpHandler);

    GrpcChannelOptions misOpcionesDelCanal = new GrpcChannelOptions()
    {
        MaxReceiveMessageSize = 62914560,
        MaxSendMessageSize = 62914560,
        HttpClient = httpClient,
    };

    // 拦截器不再依赖固定参数，每次调用时获取最新令牌
    CallCredentials misCredenciales = CallCredentials.FromInterceptor((context, metadata) =>
    {
        string? token = null;
        lock (_tokenLock)
        {
            token = _currentJwtToken;
        }

        if (!string.IsNullOrWhiteSpace(token))
        {
            metadata.Add(HeaderNames.Authorization, $"Bearer {token}");
        }
        return Task.CompletedTask;
    });

    misOpcionesDelCanal.Credentials = ChannelCredentials.Create(new SslCredentials(), misCredenciales);

    try
    {
        Uri miUri = new Uri($"{_serverAddress}:{_serverPort}");
        return GrpcChannel.ForAddress(miUri, misOpcionesDelCanal);
    }
    catch
    {
        throw new ArgumentException("服务器地址信息不正确。");
    }
}

// 提供更新令牌的方法，外部调用即可更新
public void UpdateJwtToken(string newToken)
{
    lock (_tokenLock)
    {
        _currentJwtToken = newToken;
    }
}

// 获取复用的Channel
public GrpcChannel GetCanal()
{
    return _grpcChannel;
}

关键说明 #

1. Channel复用：gRPC Channel是长生命周期对象，创建开销大（包含TCP连接建立、TLS握手等），复用能显著提升性能
2. 动态令牌逻辑：拦截器每次处理调用请求时都会读取最新的令牌，令牌过期后只需调用UpdateJwtToken传入新值即可，完全不需要重建Channel
3. 线程安全：用锁保证令牌的读写操作原子性，如果是高并发场景，也可以用Interlocked.Exchange或ConcurrentDictionary来优化

内容的提问来源于stack exchange，提问作者Álvaro García