Lines Matching refs:certificate

90   <li>Connecting to a host with a custom certificate authority(self-signed,
116   certificate or to a host whose SSL certificate is issued by a non-public CA
136   Add the self-signed or non-public CA certificate, in PEM or DER format, to
188   app can do this by specifying multiple certificate sources for a
212   certificate for your production server. In order to support this without any
277   to issue a fradulent certificate the app would be at risk from a MiTM
279   by either limiting the set of CAs they trust or by certificate pinning.
284   public key (SubjectPublicKeyInfo of the X.509 certificate). A certificate
285   chain is then only valid if the certificate chain contains at least one of
290   Note that when using certificate pinning you should always include a backup
292   pinning to a CA certificate or an intermediate of that CA), your
577     debug-overrides} are added to all other configurations and certificate
578     pinning is not performed when the server's certificate chain uses one of
649     Specifies if the CAs from this source bypass certificate pinning. If {@code
650     "true"} then certificate chains which chain through one of the CAs from this