How To: Edit Soft Token OTP Mobile App Verbiage

Follow
    Applies to:
Deployment model:
  • On Premises
  • Version Affected: All

     

    Overview

    This article explains how to edit the verbiage clients see for the Soft Token OTP Mobile App registration option, after they have already registered a mobile device.

    Registration method selection page, with the Soft Token option showing the label SecureAuth OTP Mobile App highlighted.

    On older versions of IdP (pre-9.0), the registrationmethod_oath2 data type needed to make this edit through Content and Localization is not included by default — for those versions, add it directly to Language_en.resx instead, as described in step 3 below.

     

    Edit the Soft Token OTP Mobile App Verbiage

    1. In the Admin Console, go to the realm's Overview tab, then Content and Localization under Advanced Settings.

    Realm Overview tab with Content and Localization highlighted under Advanced Settings.

    1. Find the registrationmethod_oath2 field and change its value to the desired verbiage.

    Content and Localization field for registrationmethod_oath2, with its value set to SecureAuth OTP Mobile App.

    1. If registrationmethod_oath2 is not listed in Content and Localization, open D:\Secureauth\SecureAuthX\Resource\Language_en.resx in a text editor instead, where X is the realm number.

    File Explorer showing the Resource folder for a realm, with Language_en.resx selected among the other Language_XX.resx files.

    1. Go to the bottom of the file and add a new registrationmethod_oath2 entry — copy the existing registrationmethod_oath entry and change its name and value to match. Save the file.

    Language_en.resx open in a text editor, with a registrationmethod_oath2 data entry added and its value set to SecureAuth OTP Mobile App.

    1. Go back to the realm's Content and Localization section — the new entry now appears there and can be edited the same way as step 2.

     
     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.