Beberapa produk dan fitur sedang dalam proses penggantian nama. Fitur playbook dan alur generatif juga dimigrasikan ke satu konsol gabungan. Lihat detailnya.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Webhook Agen Percakapan (Dialogflow CX) memerlukan endpoint HTTPS
yang menampilkan sertifikat TLS yang valid saat
diverifikasi menggunakan penyimpanan tepercaya default Google. Namun, Anda mungkin ingin menggunakan sertifikat
CA kustom, yang tidak dapat ditandatangani oleh certificate authority yang diakui oleh
trust store default Google. Misalnya, server webhook yang berada di dalam jaringan VPC pribadi Google memiliki masalah ini. Dalam hal ini, Anda dapat mengupload
sertifikat kustom ke Agen Percakapan (Dialogflow CX) saat membuat webhook, dan sertifikat
yang diupload akan mengganti penyimpanan tepercaya default Google.
Sertifikat CA kustom dapat berupa sertifikat yang ditandatangani sendiri atau root certificate
kustom. Anda dapat mengupload beberapa sertifikat jika ingin merotasi
sertifikat. Sertifikat harus dalam
format DER
dan harus ditandatangani dengan
nama alternatif subjek
yang cocok dengan URL webhook. Jika ekstensi keyUsage ada, nilainya harus digitalSignature.
Demo server dengan tanda tangan sendiri
Berikut adalah konfigurasi server demo:
Siapkan file sertifikat yang ditandatangani sendiri.
Kita menggunakan www.example.com sebagai domain contoh.
Mulai server HTTPS menggunakan sertifikat server (server.crt)
dan kunci pribadi (server.key) yang dibuat di langkah sebelumnya.
Kita mengasumsikan server memproses port 443.
Setelah menyiapkan server dengan sertifikat kustom, Anda dapat
membuat resource webhook
dengan petunjuk tambahan berikut untuk menggunakan sertifikat kustom:
Tetapkan URL yang cocok dengan domain yang ditandatangani dengan sertifikat
(https://www.example.com dalam demo sebelumnya).
Anda bertanggung jawab untuk memastikan bahwa domain Anda akan di-resolve dengan benar
ke alamat IP server.
Upload sertifikat kustom dalam format DER. Ini adalah file server.der dalam demo yang ditandatangani sendiri sebelumnya atau sertifikat root kustom.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eDialogflow CX webhooks, which require HTTPS endpoints, can utilize custom CA certificates when the default Google trust store is insufficient, such as for servers within Google's private VPC network.\u003c/p\u003e\n"],["\u003cp\u003eCustom certificates, either self-signed or custom root certificates, must be in DER format and include a subject alternative name that matches the webhook URL, with the optional keyUsage extension set to \u003ccode\u003edigitalSignature\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo configure a webhook with a custom certificate, the certificate file (in DER format) must be uploaded, and the webhook URL must correspond to the domain name signed by the custom certificate.\u003c/p\u003e\n"],["\u003cp\u003eService directory integrations require you to set the service directory endpoint with the IP and port of your server.\u003c/p\u003e\n"]]],[],null,["# Custom CA certificates\n\nConversational Agents (Dialogflow CX) webhooks require HTTPS endpoints\nthat present valid TLS certificates when they are\nverified using Google's default trust store. However, you may want to use custom\nCA certificates, which cannot be signed by a certificate authority recognized by\nGoogle's default trust store. For example, webhook servers that are inside\nGoogle's private VPC network have this issue. In this case, you can upload the\ncustom certificates to Conversational Agents (Dialogflow CX) when creating webhooks, and the uploaded\ncertificates will override Google's default trust store.\n\nCustom CA certificates can be self-signed certificates or custom root\ncertificates. You can upload multiple certificates in case you want to rotate\nthe certificates. The certificates must be in\n[DER format](https://en.wikipedia.org/wiki/X.509#Certificate_filename_extensions)\nand must be signed with\n[subject alternative name](https://en.wikipedia.org/wiki/Subject_Alternative_Name)\nmatching the webhook URL. When the\n[keyUsage](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.3)\nextension is present, its value needs to be `digitalSignature`.\n| **Note:** Conversational Agents (Dialogflow CX) does not support customizing the webhook client certificate to perform [mutual TLS authentication](/dialogflow/cx/docs/concept/mtls).\n\nDemo self-signed server\n-----------------------\n\nThe following is the configuration of a demo server:\n\n1. Prepare self-signed certificate files. We use www.example.com as the example domain. \n\n ```text\n openssl genrsa -out server.key 2048\n openssl req -nodes -new -sha256 -newkey rsa:2048 -key server.key -subj \"/CN=www.example.com\" -out server.csr\n openssl x509 -req -days 3650 -sha256 -in server.csr -signkey server.key -out server.crt -extfile \u003c(printf \"\\nsubjectAltName='DNS:www.example.com'\")\n openssl x509 -in server.crt -out server.der -outform DER\n ```\n2. Start your HTTPS server using the server certificate (`server.crt`) and private key (`server.key`) created in previous step. We assume the server is listening on port 443.\n3. Test to connect to the server locally. \n\n ```text\n curl --cacert server.crt https://www.example.com --resolve www.example.com:443:127.0.0.1\n ```\n\nDemo webhook with custom certificate\n------------------------------------\n\nAfter you have setup the server with your custom certificate, you may\n[create a webhook resource](/dialogflow/cx/docs/concept/webhook#create)\nwith the following extra instructions to use the custom certificate:\n\n- Set the URL matching the domain signed with the certificate (`https://www.example.com` in previous demo). It is your own responsibility to make sure that your domain will correctly resolve to the IP address of the server.\n- Upload the custom certificate in DER format. This is the `server.der` file in previous self-signed demo or the custom root certificate.\n- For webhooks integrated with [Service Directory private network access](/dialogflow/cx/docs/concept/webhook#sd), Setup your [Service Directory Endpoint](/service-directory/docs/configuring-service-directory#configure_an_endpoint) with the IP address and port of your server, and provide the [Service Directory Service](/service-directory/docs/configuring-service-directory#configure_a_service) when creating webhook."]]