Hello, Can you tell us some more about your setup - are you using gRPC built with a custom OpenSSL version, or are you using a pre-built gRPC release? Further, can you provide a code snippet of how you tried to load the private key?
We have a PrivateKeySigner API. <https://github.com/grpc/grpc/blob/3e1d845d437633917b7451bae9d226836658c0bb/include/grpc/private_key_signer.h#L35>However, using this API is only supported with the standard BoringSSL build. On Thursday, June 11, 2026 at 9:17:33 AM UTC-4 Vishakha Rastogi wrote: > Hi everyone, > > I am trying to secure a gRPC connection using OpenSSL 3 with private keys > stored in a TPM. > > The private key was generated using the TPM2 OpenSSL provider, and I can > successfully access and use the key through OpenSSL. However, when I > provide the TPM-backed private key reference/path to the gRPC server for > TLS configuration, gRPC reports that the private key is missing or cannot > be loaded. > > My questions are: > > 1. Does gRPC support TPM2/OpenSSL provider-based keys directly? > 2. Is there a way to configure gRPC to use a TPM-backed private key > without exporting the key material? > 3. Has anyone successfully integrated OpenSSL 3 providers > (specifically TPM2 provider) with gRPC TLS credentials? > > Environment: > > - gRPC: 1.62.0 > - OpenSSL: 3.2.6 > - TPM2 OpenSSL Provider: 1.1.1 > > Any guidance or examples would be greatly appreciated. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/06cfce3a-53a9-49a5-abcd-fa95373a2ac0n%40googlegroups.com.
