Hi, in the register page a custom server can be used to define "where to connect to". Your system does not validate the SSL certificate of this host which makes it easy to tamper with the data your system do in behalf of the user. As only SSL links are allowed by the application the user could assume that the implementation is according to security best practice and would validate the certificate trustchain on connect. Additional "relateiq" might can guarantee the security of any connection under control, but the connection made over insecure networks could be tampered by anyone with access to this system. I have used ncat which generates a certificate on the fly to demonstrate the issue: ncat --ssl -p 443 -v -n -l Ncat: Version 6.46 ( http://nmap.org/ncat ) Ncat: Generating a temporary 1024-bit RSA key. Use --ssl-key and --ssl-cert to use a permanent one. Ncat: SHA-1 fingerprint: 541F EC41 71A1 BDDC D7AE DA96 8950 5584 4BC5 E9D3 Ncat: Listening on :::443 Ncat: Listening on 0.0.0.0:443 Ncat: Connection from 54.218.20.199. Ncat: Connection from 54.218.20.199:53669. POST / HTTP/1.1 Content-Type: text/xml; charset=utf-8 Accept: text/xml User-Agent: ExchangeServicesClient/15.00.0516.014 Accept-Encoding: gzip,deflate Host: pum.no-ip.org X-ClientStatistics: MessageId=0ba62fc8-5767-4578-b789-0951dcf8e559,ResponseTime=389,SoapAction=FindItem`1; Content-Length: 1464 Expect: 100-continue Connection: Keep-Alive AllProperties cheers pUm

RelateIQ: Failed Certificate Validation On Custom Server (Register)