![]() Use a certificate file as the server certificate and any intermediate or chained certificates. Select in the box to browse for the file.Ī private key file must be encoded as a PKCS #8 file. Drag and drop a private key, certificate file, or a keystore file.Select the Update Server Certificate button.To replace the server private key and server certificate: For more information, see Update ClientĬertificate Trust Mode window and Update Server Certificate Trust Mode window. Server trust modes are configured to trust the new certificate. ExtremeCloud IQ - Site Engine clients and other serversĬertificates using the client certificate trust mode and server certificate trust mode settings.īefore updating the ExtremeCloud IQ - Site Engine server certificate, be sure that the client and Whenever the ExtremeCloud IQ - Site Engine server certificate is changed, other ExtremeCloud IQ - Site Engine componentsĬan be affected by the change and stop trusting the server. The following steps assume you generated a replacement server Openssl pkcs8 -topk8 -in -out server-pkcs8.key -nocrypt The server.key file can be copied and converted on either engine.) (OpenSSL is available on ExtremeCloud IQ - Site Engine and ExtremeControl engines. ![]() Use the following OpenSSL command where is the original non‑PKCS #8 formatted key file to convert your key file to a PKCS #8 format. ExtremeCloud IQ - Site Engine also accepts PKCS#12 keystore files, which can contain both a private key and certificates. Individual files, in a bundle file, or in the same file as the serverĬertificate. Use the intermediateĬertificates in whatever format the CA provides them: in If your certificate authority (CA) provides additional intermediateĬertificates, provide those as well. "browser-friendly" certificates, the server certificate should identify theĮxtremeCloud IQ - Site Engine server by its fully qualified host name. Generate the server certificate using the RSA or DSA server private key
0 Comments
Leave a Reply. |