Class: Google::Cloud::Dialogflow::CX::V3::Tool::TLSConfig
- Inherits:
-
Object
- Object
- Google::Cloud::Dialogflow::CX::V3::Tool::TLSConfig
- Extended by:
- Protobuf::MessageExts::ClassMethods
- Includes:
- Protobuf::MessageExts
- Defined in:
- proto_docs/google/cloud/dialogflow/cx/v3/tool.rb
Overview
The TLS configuration.
Defined Under Namespace
Classes: CACert
Instance Attribute Summary collapse
Instance Attribute Details
#ca_certs ⇒ ::Array<::Google::Cloud::Dialogflow::CX::V3::Tool::TLSConfig::CACert>
Returns Required. Specifies a list of allowed custom CA certificates for HTTPS verification.
399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 |
# File 'proto_docs/google/cloud/dialogflow/cx/v3/tool.rb', line 399 class TLSConfig include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # The CA certificate. # @!attribute [rw] display_name # @return [::String] # Required. The name of the allowed custom CA certificates. This # can be used to disambiguate the custom CA certificates. # @!attribute [rw] cert # @return [::String] # Required. The allowed custom CA certificates (in DER format) for # HTTPS verification. This overrides the default SSL trust store. If this # is empty or unspecified, Dialogflow will use Google's default trust # store to verify certificates. N.B. Make sure the HTTPS server # certificates are signed with "subject alt name". For instance a # certificate can be self-signed using the following command: # # ``` # openssl x509 -req -days 200 -in example.com.csr \ # -signkey example.com.key \ # -out example.com.crt \ # -extfile <(printf "\nsubjectAltName='DNS:www.example.com'") # ``` class CACert include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end end |