RSA Authentication Manager
RSA Authentication Manager can be configured to utilize Spryng SMS Gateway for delivery of ondemand tokencodes to be used in on-demand authentications. When a user authenticates to an agent using his/her username and on-demand PIN, the RSA Authentication Manager sends the on-demand tokencode and mobile number to Spryng SMS Gateway using the HTTP or HTTPS protocol. Spryng SMS Gateway then delivers the on-demand tokencode to the user’s mobile device via Short Message Service (SMS.) The authentication process is completed when the user enters the on-demand tokencode into the agent’s prompt for next tokencode.
SMS PASSCODE supports transmission of passcode messages and notifications by SMS. SMS PASSCODE v8.0 includes a pluggable transmission infrastructure that allows transmission of messages using any transmission mechanism that is available using a server-based API. This makes it possible to send messages by using the SMS Gateway of Spryng.
One-time passwords, or OTP, are used for a single session or transaction. F5’s BIG-IP APM can be employed to generate the OTP and pass it to the user via the SMS Gateway of Spryng, eliminating the need for a token creating server/security appliance while reducing cost and complexity.
Gemalto and Spryng are working together to provide passwords, login and authentication codes by SMS, enabling fast and reliable authentication to take place. Using Gemalto SafeNet Authentication Service (SAS), the SMS Gateway of Spryng can be configured by the customer. This document outlines how to incorporate Spryng as SMS service provider.
With the SecurEnvoy Soft Token, the users’ mobile phone can receive a one-time passcode (OTP) via SMS. SecurEnvoy provides a great range of tokenless types: the passcode sent via SMS can be delivered in real time, pre-loaded as an OTP, pre-loaded with 3 OTP or a reusable Daycode.
SonicWALL and Spryng cooperate to provide One-Time Passwords (OTP) and authentication codes. This can effectively reduce costs and processes are made more efficient because physical tokens are not longer needed. The user simply receives the one-time password via SMS on its mobile phone.
Spryng and SAP have been cooperating for a substantial amount of time to enable the sending of codes by SMS for all kinds of purposes. SMS messages can be sent through SAP via both HTTP and (E)SMTP. This manual shows the step by step procedure to configure SAP SMS through HTTP.