Rest APIs : REST API : Getting started : Understanding self-signed certificates
Understanding self-signed certificates
Observer Platform uses a self-signed certificate. Find out why that’s not as scary as it sounds.
A website that uses encryption must use a certificate. A certificate is used to ensure that the website you are going to is actually the website you expect and not a malicious site looking to steal your information. You know a website is using encryption when the URL begins with https rather than http. Another way you know is that the browser displays a “padlock” icon in the address bar.
To trust a certificate you must trust the company and the certificate authority. Certificate authorities are neutral, third-party organizations that approve certificates and do so by verifying certain information about the company wishing to have their certificate granted.
This process does not exist with self-signed certificates. By its very nature a self-signed certificate is less secure than one that has been verified by a third-party; however, it is still a matter of trust. We feel that we’re trustworthy, and you probably trust us too since you’re using our products. It’s for that reason that we feel our self-signed certificate is just as good as a certificate approved by a certificate authority and you should accept it.
The thumbprint or fingerprint for our products:
Apex
‎53 12 c3 2d af 3f c7 a3 3d fc 22 25 52 3c a2 35 bb 43 ad 0e
OMS
de fa 6e 7c 3e 5a e7 ef 10 e2 5d ae 9c 3b 4f 0c c6 44 9e a8