Package io.grpc
Class TlsServerCredentials.Builder
java.lang.Object
io.grpc.TlsServerCredentials.Builder
- Enclosing class:
TlsServerCredentials
Builder for
TlsServerCredentials
.-
Method Summary
Modifier and TypeMethodDescriptionbuild()
Construct the credentials.clientAuth
(TlsServerCredentials.ClientAuth clientAuth) Indicates whether the server should expect a client's identity.keyManager
(File certChain, File privateKey) Use the provided certificate chain and private key as the server's identity.keyManager
(File certChain, File privateKey, String privateKeyPassword) Use the provided certificate chain and possibly-encrypted private key as the server's identity.keyManager
(InputStream certChain, InputStream privateKey) Use the provided certificate chain and private key as the server's identity.keyManager
(InputStream certChain, InputStream privateKey, String privateKeyPassword) Use the provided certificate chain and possibly-encrypted private key as the server's identity.keyManager
(KeyManager... keyManagers) Have the provided key manager select the server's identity.RequiresTlsServerCredentials.Feature.FAKE
to be understood.trustManager
(File rootCerts) Use the provided root certificates to verify the client's identity instead of the system's default.trustManager
(InputStream rootCerts) Use the provided root certificates to verify the client's identity instead of the system's default.trustManager
(TrustManager... trustManagers) Have the provided trust manager verify the client's identity instead of the system's default.
-
Method Details
-
requireFakeFeature
RequiresTlsServerCredentials.Feature.FAKE
to be understood. For use in testing consumers of this credential. -
keyManager
Use the provided certificate chain and private key as the server's identity. Generally they should be PEM-encoded and the key is an unencrypted PKCS#8 key (file headers have "BEGIN CERTIFICATE" and "BEGIN PRIVATE KEY").- Throws:
IOException
-
keyManager
public TlsServerCredentials.Builder keyManager(File certChain, File privateKey, String privateKeyPassword) throws IOException Use the provided certificate chain and possibly-encrypted private key as the server's identity. Generally they should be PEM-encoded and the key is a PKCS#8 key. If the private key is unencrypted, then password must benull
.- Throws:
IOException
-
keyManager
public TlsServerCredentials.Builder keyManager(InputStream certChain, InputStream privateKey) throws IOException Use the provided certificate chain and private key as the server's identity. Generally they should be PEM-encoded and the key is an unencrypted PKCS#8 key (file headers have "BEGIN CERTIFICATE" and "BEGIN PRIVATE KEY").- Throws:
IOException
-
keyManager
public TlsServerCredentials.Builder keyManager(InputStream certChain, InputStream privateKey, String privateKeyPassword) throws IOException Use the provided certificate chain and possibly-encrypted private key as the server's identity. Generally they should be PEM-encoded and the key is a PKCS#8 key. If the private key is unencrypted, then password must benull
.- Throws:
IOException
-
keyManager
Have the provided key manager select the server's identity. Although multiple are allowed, only the first instance implementing a particular interface is used. So generally there will just be a single entry and it implementsX509KeyManager
. -
clientAuth
Indicates whether the server should expect a client's identity. Must not benull
. Defaults toTlsServerCredentials.ClientAuth.NONE
. -
trustManager
Use the provided root certificates to verify the client's identity instead of the system's default. Generally they should be PEM-encoded with all the certificates concatenated together (file header has "BEGIN CERTIFICATE", and would occur once per certificate).- Throws:
IOException
-
trustManager
Use the provided root certificates to verify the client's identity instead of the system's default. Generally they should be PEM-encoded with all the certificates concatenated together (file header has "BEGIN CERTIFICATE", and would occur once per certificate).- Throws:
IOException
-
trustManager
Have the provided trust manager verify the client's identity instead of the system's default. Although multiple are allowed, only the first instance implementing a particular interface is used. So generally there will just be a single entry and it implementsX509TrustManager
. -
build
Construct the credentials.
-