SharpV units must communicate using TLS encryption (HTTPS) using either the certificate that is auto-generated on the SharpV, 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 Sharp unit, a self-signed certificate is generated and HTTPS is activated by default.
- Install the certificate on all machines that communicate with the SharpV 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 SharpV 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 section displays the Security Center connection as Unauthorized.
- If you are configuring a SharpV G1 or G2 unit running SharpOS 12.6 or earlier, it is recommended that you use an HTTPS connection while connecting to the Sharp Portal. This requires a self-signed certificate or one issued by a trusted certificate authority (CA) to be installed on the SharpV unit. SharpOS 12.7 GA and later require HTTPS to operate and must use a certificate. A self-signed certificate is automatically created for a unit that does not already have one.