Smart Hub authentication
The Smart Hub uses certificates for authentication with its clients that include Smart Agents and Application Server. The Smart Hub communication with its clients is established after you complete the following tasks:
- Provide a shared secret key (SSK) during Smart Hub installation.
- Provide the same SSK while registering the Smart Hub in the Application Server.
- Configure the Smart Agent to specify the Smart Hub details, such as host name, port number, and the access key.
The authentication mechanism works as follows:
Authentication between the Smart Hub and Application Server
- The Application Server sends a certificate signing request (CSR) to the Smart Hub along with the authentication details created using SSK.
- The Smart Hub verifies the authentication details using SSK. It acts as a private CA and has its own signer certificates.
- The Smart Hub creates a signed certificate, and sends it to the Application Server. The certificate includes the public key.
- The Application Server saves the certificate in the database and displays it as an encoded access key on the UI.
- The Application Server uses this stored certificate during the future communication with the Smart Hub.
Authentication between the Smart Hub and Smart Agents
- The Smart Agent sends a certificate signing request (CSR) to the Smart Hub along with the authentication details created using the access key.
- The Smart Hub verifies the details using the private key.
- The Smart Hub issues a certificate to the Smart Agent.
- The Smart Agent saves the signed certificate and uses it for all the future communication with the Smart Hub.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*