[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Web TLS certificate configuration\n\nGoogle Distributed Cloud (GDC) air-gapped appliance provides a [public key infrastructure (PKI) API](/distributed-cloud/hosted/docs/latest/appliance/apis/service/security/pki/v1/security-pki-v1)\nfor you to obtain a web certificate. This API supports several user modes:\n\n- **Fully-managed**: certificates issued by GDC PKI infrastructure and chained to a GDC-managed self-signed root certificate authority (CA).\n- **BYO cert**: you provide a pool of certificates with a default wildcard certificate. GDC will use the best matched certificate for your service.\n- **BYO SubCA**: certificates issued by GDC PKI infrastructure and chained to your SubCA. You must provide the SubCA and let GDC operate it.\n\nInfra PKI mode definitions\n--------------------------\n\nThis section provides a detailed explanation of each PKI user mode.\n\n### Fully Managed mode (default mode)\n\nIn fully managed mode, the tenant organization relies on the GDC\npublic key infrastructure (PKI) to issue certificates. When you create a new\norganization, this mode is the default mode applied. Afterwards, you can switch\nto a different PKI mode.\n\nWith this mode, you must obtain and distribute the root CA to your environment\nfor trust.\n\n### BYO Certificates mode\n\nBYO certificate mode supports signing leaf certificates with external or user-managed\nCAs. This mode generates a certificate signing request (CSR) for every\ncertificate request. While waiting for signing, BYO cert mode searches for an\nexisting customer-signed certificate among the pool that matches with the\ncertificate request:\n\n- If it can't find a matching certificate, a GDC-managed fallback CA issues a temporary certificate ready for immediate use.\n- If it finds a matching certificate, it uses the matching certificate as the temporary certificate for the current request.\n\nTo sign the CSR, you must perform the following steps:\n\n1. Download the CSR from the `Certificate` custom resource status.\n2. Upload the signed certificate and the external CA certificate to the same `Certificate` custom resource with an update to the `spec` field.\n\nTo manage verification and replace the temporary certificate, GDC air-gapped appliance\nupdates the certificate secret with the uploaded certificate and the external CA.\nYou don't have to change your trust stores.\n\nFor more information, see\n[Sign the BYO certificate](/distributed-cloud/hosted/docs/latest/appliance/platform/pa-user/pki/transition-pki-modes#sign-byo-cert).\n\n### BYO SubCA mode\n\nWith BYO SubCA mode, a CSR for the SubCA generates within the GDC air-gapped appliance\nManagement API server. You must sign the CSR request, and upload the signed\ncertificate into the system. For more information, see\n[Sign the BYO SubCA certificate](/distributed-cloud/hosted/docs/latest/appliance/platform/pa-user/pki/transition-pki-modes#sign-byo-subca-cert).\nYou can create a `CertificateIssuer` custom resource that points to this SubCA\nand mark it as the default `CertificateIssuer`.\n\nThe newly created subCA issues all of the subsequent web certificates. You\ndon't have to change your trust stores.\n\nTransition to a different PKI mode\n----------------------------------\n\nThe PKI API supports transition from the default fully-managed mode to other\nsupported custom modes. For more information, see\n[transition to different PKI modes](/distributed-cloud/hosted/docs/latest/appliance/platform/pa-user/pki/transition-pki-modes)."]]