After installing a parser, if you see a warning on the parser configuration page indicating that the connection is not private, then the SSL certificate of the parser is missing. You can secure the connection by associating an SSL certificate to the parser.
Cause
By default, the parser uses the certificate of the hosted machine, but the domain name of the certificate and parser may not match. If this happens, then a warning that the connection is not private is shown on the parser configuration page.
Solution
Associate an SSL certificate, which includes the domain name where the parser is hosted, to the parser:
- Import the certificate into the following repositories in the system where the parser is installed:
- Trusted People\Certificates
- Trusted Root Certification Authorities\Certificates
- Add the thumbprint of the certificate to configuration.json, which is located in the parser installer folder.
