
A certificate will be exchanged from a node A to another node B.There are a number of occasions in which certificates are not used by a server only, but also used by a client that is using a certificate to authenticate to a server.Īll these certificate exchanges have one thing in common: These are however not compatible with each other as each implementation can be done differently. The secure RADIUS implementation known as RADSEC, rfc6614, also uses TLS.Īlso, there are, since TLS works as a tunnel in which payload is transferred, VPN solutions based on SSL or TLS, that supersedes SSL. EAP methods that use TLS: EAP-TLS, EAP-TTLS, EAP-PEAP. Its extensible authentication protocol (EAP) can extend the functionality/security of RADIUS greatly. If the tunnel cannot be established, the payload will not be sent. These protocols are working simply by creating a TLS tunnel prior to sending, or transporting, any protocol respective payload. FTPS (not to be mixed up with SFTP which is FTP over SSH).SMTPS (and a compatibility idea called ‘STARTTLS’).One indicator is the ‘S’ at the end of some protocols, SMTP(S), LDAP(S), FTP(S) are such examples. Where the payload is coming from often does not matter. Digital certificates are typically used to build up TLS tunnels in various products, FortiClientEMS, FortiAnalzyer, FortiGate, FortiNAC, FortiAuthenticator, FortiWeb, and many more.Īll of them use certificates already with the web server so where the graphical user interface is available.Īdditional functions like Agents or client applications may also make use of certificates.Ĭertificates generally will be used for encrypting payload. This article tries to give more insight into digital certificates, their use, and validation.
