Features/Mass Deployment/Setting Files/XML/Certificates

From Snom User Wiki

(Difference between revisions)
Jump to: navigation, search
(Introduction)
(Introduction)
Line 19: Line 19:
The benefit of this variant is, that the certificate is immediately available after processing the line in the provisioning XML.
The benefit of this variant is, that the certificate is immediately available after processing the line in the provisioning XML.
 +
You can get the bas64 encoded certificate out of the PEM format, removing the BEGIN / END taglines:
 +
 
 +
  -----BEGIN CERTIFICATE-----
 +
 +
  -----END CERTIFICATE-----
For further description please see the detailed [[Networking/Transport_Layer_Security_(TLS)]]
For further description please see the detailed [[Networking/Transport_Layer_Security_(TLS)]]

Revision as of 11:21, 12 October 2018

Introduction

The certificates settings (<certificates> tag) contains the trusted server certificates. This XML tag can be used either

The tag contains an attribute with the URL of the certificate file to fetch:

 <certificate url="http://some.url/certificate.der" />

Please note that the download of the certificate is delayed after all provisioning xml files have been loaded and processed.

Beginning with firmware release 8.7.5.52/8.9.3.41 a second variant of this tag is supported, where the content of the certificate file is included as a base64 encoded string:

 <certificate type="base64">...</certificate>

The benefit of this variant is, that the certificate is immediately available after processing the line in the provisioning XML. You can get the bas64 encoded certificate out of the PEM format, removing the BEGIN / END taglines:

 -----BEGIN CERTIFICATE-----
 -----END CERTIFICATE-----

For further description please see the detailed Networking/Transport_Layer_Security_(TLS)

Personal tools
Interoperability