Java GRPC客户端传递元数据遇认证错误，求解决方案

问题分析 #

你的代码存在几个关键问题：

• callCredentials变量未实例化，直接调用会触发空指针异常
• 手动调用metadataApplier.apply()和callCredentials.applyRequestMetadata()是错误逻辑，这些方法由gRPC框架在发起请求时自动触发，无需用户手动调用
• 使用Mock的RequestInfo、Executor、MetadataApplier完全没必要，这些是gRPC内部依赖，不需要用户模拟

解决方案 #

方案一：自定义CallCredentials（推荐用于动态生成凭证的场景）

实现专属的CallCredentials类，在框架回调方法中注入所需元数据：

public class CustomCallCredentials extends CallCredentials {
    private final String clientId;
    private final String workerId;
    private final String instance;

    public CustomCallCredentials(String clientId, String workerId, String instance) {
        this.clientId = clientId;
        this.workerId = workerId;
        this.instance = instance;
    }

    @Override
    public void applyRequestMetadata(RequestInfo requestInfo, Executor executor, MetadataApplier metadataApplier) {
        executor.execute(() -> {
            try {
                Metadata headers = new Metadata();
                Metadata.Key<String> clientidKey = Metadata.Key.of("clientid", Metadata.ASCII_STRING_MARSHALLER);
                Metadata.Key<String> workeridKey = Metadata.Key.of("workerid", Metadata.ASCII_STRING_MARSHALLER);
                Metadata.Key<String> instanceKey = Metadata.Key.of("instance", Metadata.ASCII_STRING_MARSHALLER);
                
                headers.put(clientidKey, clientId);
                headers.put(workeridKey, workerId);
                headers.put(instanceKey, instance);
                
                metadataApplier.apply(headers);
            } catch (Exception e) {
                metadataApplier.fail(Status.UNAUTHENTICATED.withCause(e));
            }
        });
    }

    @Override
    public void thisUsesUnstableApi() {
        // 留空即可，标记使用gRPC不稳定API
    }
}

调用Stub时绑定自定义凭证：

public void add(String target, int instanceId) throws InterruptedException {
    ManagedChannel channel = ManagedChannelBuilder.forTarget(target)
            .usePlaintext()
            .build();
    BlockingStub stub = newBlockingStub(channel);
    
    // 初始化自定义凭证
    CallCredentials credentials = new CustomCallCredentials("1", "2", Integer.toString(instanceId));
    
    // 绑定凭证并发起请求
    stub.withCallCredentials(credentials).add(Empty.newBuilder().build());
    
    channel.shutdown().awaitTermination(5, TimeUnit.SECONDS);
}

方案二：直接通过Stub添加元数据（更简便，适合固定/简单动态元数据）

如果不需要复杂的凭证生成逻辑，直接给Stub注入元数据即可，无需使用CallCredentials：

public void add(String target, int instanceId) throws InterruptedException {
    ManagedChannel channel = ManagedChannelBuilder.forTarget(target)
            .usePlaintext()
            .build();
    BlockingStub stub = newBlockingStub(channel);
    
    Metadata headers = new Metadata();
    Metadata.Key<String> clientidKey = Metadata.Key.of("clientid", Metadata.ASCII_STRING_MARSHALLER);
    Metadata.Key<String> workeridKey = Metadata.Key.of("workerid", Metadata.ASCII_STRING_MARSHALLER);
    Metadata.Key<String> instanceKey = Metadata.Key.of("instance", Metadata.ASCII_STRING_MARSHALLER);
    
    headers.put(clientidKey, "1");
    headers.put(workeridKey, "2");
    headers.put(instanceKey, Integer.toString(instanceId));
    
    // 通过CallOptions绑定元数据
    stub.withCallOptions(CallOptions.DEFAULT.withMetadata(headers))
            .add(Empty.newBuilder().build());
    
    channel.shutdown().awaitTermination(5, TimeUnit.SECONDS);
}

额外注意事项 #

• 确保服务端期望的元数据Key名称和你使用的完全一致（大小写敏感）
• 生产环境禁止使用usePlaintext()，需配置TLS加密传输
• 若需全局给所有请求添加元数据，可使用ClientInterceptor在interceptCall方法中统一注入

内容的提问来源于stack exchange，提问作者Павел Тишков