Configure On-Demand Tokencode Delivery

Document created by RSA Information Design and Development on Jun 13, 2017Last modified by RSA Information Design and Development on Jun 13, 2017
Version 2Show Document
  • View in full screen mode

If you plan to use on-demand tokencodes as an authentication method, you must use the Security Console to configure the deployment to send on-demand tokencodes. RSA Authentication Manager can deliver on-demand tokencodes in two ways:

  • To mobile phones by text message. You can configure an SMS provider or modem to integrate with Authentication Managerto deliver on-demand tokencodes to a user’s mobile phone. Use the parameters required by the SMS provider or modem vendor.

  • To e-mail accounts. You must configure a connection to a Simple Mail transfer Protocol (SMTP) server.

You can select only one delivery method, either mobile phone or e-mail, per user.

Before you begin 

  • If you plan to configure tokencode delivery by text message, ensure that Authentication Manager has access to the identity source attributes where you store mobile phone numbers. Authentication Manager automatically maps to the mobile attributes in the internal database and an LDAP directory.

  • (Optional) Using the Security Console, you can map to custom attributes in the internal database and an LDAP directory. See Identity Attribute Definitions for On-Demand Tokencode Delivery by Text Message.

  • If you plan to configure tokencode delivery to a user’s e-mail address, confirm that your e-mail is managed by an SMTP server.

  • Make sure that all users’ destination mobile phone numbers meet the following requirements:

    • The mobile phone numbers must include country codes. If they are not already stored with country codes, select a country code when you configure on-demand tokencode delivery to mobile phones.

    • End the mobile phone number with a number.

    • The mobile phone number may begin with the plus (+) character.

    • Use the following characters or a blank space for separators: . - ( ).

    • Do not use alphabetic characters or any other characters not mentioned in this list.

    The following are examples of valid destination mobile phone numbers:

    +1 123 123 1234

    +44 1234-123-123-1

    123 123 1234

    123.123.1234

    (123) 123-1234

Procedure 

  1. In the Security Console, click Setup > System Settings.

  2. Click On-Demand Tokencode Delivery.

  3. On the SMS Configuration tab, specify the user attributes that will be used to provide the tokencode destination information and manage plug-in configurations.

  4. Test the SMS Provider Integration.

  5. If the provider integration test is successful, click Save.

  6. On the E-mail Configuration tab, specify the user attribute that will be used to provide the tokencode destination information.

  7. Click Save.

  8. On the Tokencode Settings tab, specify the on-demand tokencode message text that users receive and the message lifetime.

  9. Click Save.

 

 

 

 


Attachments

    Outcomes