How to change message seen by end user's mobile phone in RSA Mobile Authentication Server 1.5
Originally Published: 2004-05-20
Article Number
Applies To
Microsoft Windows 2000 Advanced Server SP4
Issue
Some parts of the SMS message cannot be altered
Cause
Tokencode::
12345678
(Message#: AD200123)
RSA Mobile
Authentication
Some parts of this message may be customized by the administrator (see How to update RSA Mobile SMS Configuration) however two key parts of the message may not be altered.
The 8-digit tokencode, which in the above example the value is "12345678"
The message ID to compare with a prompt on an authentication page, which above reads "(Message#: AD200123)"
These 2 components are considered to be the bare minimum of an SMS message. During an standard authentication, the user will see a message along the lines of "use the tokencode associated with message # AD200123", at this point they would type in "12345678". This allows for users who may have inadvertently left old messages on their phone, and can scroll through to find the correct (up to date) tokencode value. All other parts may be changed or removed.
Resolution
Related Articles
RSA Cloud Authentication Service End User Videos Number of Views Preventing end users from bypassing the RSA SecurID Access Cloud Authentication Service Number of Views Skyhigh End User Remediation Flow - RSA Ready Implementation Guide Number of Views Skyhigh End User Remediation Flow - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views On-Demand Tokencode Delivery by Mobile Phone or E-Mail Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
