Authenticator - VPN Secure Token Replacement - VPN Authentication Login Triggered

<< <%SKIN-STRTRANS-SYNCTOC%> >>

Authenticator - VPN Secure Token Replacement - VPN Authentication Login Triggered

 

 

 

Step 1: Customer logs into their VPN client with their username and password

 

Step 2: The NAS receives the request

 

Step 3.1: NAS makes an authentication request to the Authenticator server

 

Step 3.2: As no SMS Token was included the request was incomplete

 

Step 4.1 / 4.2: The NAS triggers the VPN Client to prompt for a SMS token.

 

Step 5.1 / 5.2: The Authentication server sends an SMS with the SMS token to the user.

 

Step 6.1: The user enters the SMS token into the VPN

 

Step 6.2: The NAS receives the SMS token

 

Step 7.1 The NAS requests validation of the complete set of parameters: username/password/SMS token

 

Step 7.2: The Authenticator server grants authorization.