<< <%SKIN-STRTRANS-SYNCTOC%> >> Authenticator - VPN Secure Token Replacement - User Triggered |
VPN Secure tokens can be granted either through a request from the user via a VPN login, or via an SMS Inbound request.
The following scenario relates to the use case where a user requests an SMS Token, by submitting a 'Mobile Originated' SMS.
Step 1.1: Customer requests a token by sending an SMS to a number with a keyword, e.g. 'TOKEN'
Step 1.2: The SMSC forwards the message on to the Authenticator server.
Step 2.1: The Authenticator service responds back with an SMS Token.
Step 3: User starts up VPN Client, enters username, password, and SMS token
Step 4: NAS receives the authentication parameters from the user.
Step 5: The NAS requests for authentication authorization from the Authenticator server
Step 6: The Authenticator server provides success/failure to the NAS to the request to grant authorization.