Encrypting the connection to the SharpZ3 web portal (Basic) - SharpZ3 units must communicate using TLS encryption (HTTPS) using either the certificate that is auto-generated on the SharpZ3, a new self-signed certificate, or a signed certificate from your own public key infrastructure (PKI) or from a Certificate Authority such as VeriSign. - Security Center 5.12

Security Center Hardening Guide 5.12
Product
Security Center
Content type
Guides > Administrator guides
Version
5.12
ft:locale
en-US
Last updated
2024-12-17

SharpZ3 units must communicate using TLS encryption (HTTPS) using either the certificate that is auto-generated on the SharpZ3, a new self-signed certificate, or a signed certificate from your own public key infrastructure (PKI) or from a Certificate Authority such as VeriSign.

Consider the following:

  • The first time you power up the SharpZ3 unit, a self-signed certificate is generated and HTTPS is activated by default.
  • Install the certificate on all machines that communicate with the SharpZ3 unit. This includes the servers hosting the ALPR Manager, the Archiver, and all machines that connect to the Sharp Portal.
  • You can install multiple certificates and then select a certificate to activate.
    IMPORTANT: If the current certificate is a signed certificate, deleting the Certificate Signing request prevents the certificate from being reinstalled.
  • If the IP address of the SharpZ3 changes, you must regenerate and reinstall the signed or self-signed certificate.
  • If certificate validation fails either on the Security Center server or on the SharpV unit, the Sharp Portal Dashboard > Overview > Connectivity section displays the Security Center connection as Unauthorized.