Update from SAP DITA CMS (squashed):

commit 01519b4af1c694a5236b53a766e91e7db9ca6b93
Author: REDACTED
Date:   Mon Jul 7 11:18:51 2025 +0000

    Update from SAP DITA CMS 2025-07-07 11:18:51

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit e9a904c40c3b1089a5bacb1314155e08cbbaa964
Author: REDACTED
Date:   Mon Jul 7 11:07:35 2025 +0000

    Update from SAP DITA CMS 2025-07-07 11:07:35

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit 04705e2ca600e399c0c3f9c830ebfd6546b01c63
Author: REDACTED
Date:   Mon Jul 7 10:54:51 2025 +0000

    Update from SAP DITA CMS 2025-07-07 10:54:51

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/1-connectivity-documentation/certificate-types-007e405.md

@@ -0,0 +1,55 @@
+<!-- loio007e40560d7a4a7b846d1eaeb44f8e94 -->
+
+# Certificate Types
+
+Find information on different certificate types you can use to configure destinations in your SAP BTP subaccount.
+
+
+<table>
+<tr>
+<th valign="top">
+
+Certificate Type
+
+</th>
+<th valign="top">
+
+Description
+
+</th>
+</tr>
+<tr>
+<td valign="top">
+
+Single \(X.509\) Certificate
+
+</td>
+<td valign="top">
+
+Binds an identity to a public key using a digital signature. A certificate contains an identity \(hostname, organization, or individual\) and a public key. It is either signed by a certificate authority or is self-signed.
+
+Supported file formats: PEM, CER, CRT
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Key Store Certificate
+
+</td>
+<td valign="top">
+
+Certificate stored in a key store repository, containing the public and private key of the certificate.
+
+Supported file formats: JKS, PFX, P12
+
+> ### Restriction:  
+> Key stores are not supported in environments based on FIPS \(*Federal Information Processing Standard*\).
+
+
+
+</td>
+</tr>
+</table>
+

docs/1-connectivity-documentation/manage-destination-certificates-df1bb55.md

@@ -183,3 +183,5 @@ You can maintain truststore and keystore certificates in the *Destinations* edit
 
 [Manage Trust](manage-trust-82dbeca.md)
 
+[Certificate Types](certificate-types-007e405.md)
+

docs/index.md

@@ -123,6 +123,7 @@
                 -   [Create Destinations on Service Instance Creation](1-connectivity-documentation/create-destinations-on-service-instance-creation-43c0538.md)
             -   [Manage Destination Fragments](1-connectivity-documentation/manage-destination-fragments-b085906.md)
             -   [Manage Destination Certificates](1-connectivity-documentation/manage-destination-certificates-df1bb55.md)
+                -   [Certificate Types](1-connectivity-documentation/certificate-types-007e405.md)
             -   [Manage Trust](1-connectivity-documentation/manage-trust-82dbeca.md)
             -   [Create and Bind a Destination Service Instance](1-connectivity-documentation/create-and-bind-a-destination-service-instance-9fdad3c.md)
                 -   [Use a Config.JSON to Create or Update a Destination Service Instance](1-connectivity-documentation/use-a-config-json-to-create-or-update-a-destination-service-instance-6816d3c.md)