Secure Mobile Access 100 10.2 Administration Guide

SSL Handshake Procedure

The following procedure is an example of the standard steps required to establish an SSL session between a user and an SMA gateway using the Secure Mobile Access web-based management interface:

  1. When a user attempts to connect to the SMA appliance, the user’s Web browser sends information about the types of encryption supported by the browser to the appliance.
  2. The appliance sends the user its own encryption information, including an SSL certificate with a public encryption key.
  3. The Web browser validates the SSL certificate with the Certificate Authority identified by the SSL certificate.
  4. The Web browser generates a pre-master encryption key, encrypts the pre-master key using the public key included with the SSL certificate and sends the encrypted pre-master key to the SMA gateway.
  5. The SMA gateway uses the pre-master key to create a master key and sends the new master key to the user’s Web browser.
  6. The browser and the SMA gateway use the master key and the agreed upon encryption algorithm to establish an SSL connection. From this point on, the user and the SMA gateway encrypts and decrypts data using the same encryption key. This is called symmetric encryption.
  7. After the SSL connection is established, the SMA gateway encrypts and sends the Web browser the SMA gateway login page.
  8. The user submits their username, password, and domain name.
  9. If the user’s domain name requires authentication through a RADIUS, LDAP, or Active Directory Server, the SMA gateway forwards the user’s information to the appropriate server for authentication.
  10. After being authenticated, the user can access the Secure Mobile Access portal.

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.