Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-15621

XUI: Forgot Username flow will return incorrect string when completing flow

    Details

    • Type: Bug
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: 6.5.2, 6.5.2.1
    • Fix Version/s: None
    • Component/s: self-service, XUI
    • Labels:
    • Rank:
      1|hzzcvr:

      Description

      Bug description

      The following message will be displayed when completing the forgot username flow with both Email username and Show Username not enabled (which is a misconfiguration anyway - as the username cannot be revealed to the user in this scenario...Perhaps the real question in this Jira should be, should we even allow this set up?)

      How to reproduce the issue

      1. Deploy AM 6.5.2 and login as amAdmin
      2. Add and Configure a "User Self Service" service against the top realm using default configuration values.
      3. From the Forgotten Username tab ensure that "Email Username" and "Show Username" are disabled.
      4. Create a test user (via Identities > Add Identity)which you can then use to test the forgot username flow.
      5. Logout as amAdmin
      6. From the login screen click the "Forgot Username?" link (don't forget to clear your browser cache if this link doesn't appear)
      1. Enter the details of the identity you just created.
      2. View the output message on the following screen.
      Expected behaviour
      A success message should be displayed to the user
      
      Current behaviour
      common.user.forgotUsername.completed is displayed

      Code analysis

      It looks as though an entry is missing from the translation.json file for the forgotUsername string entries. One was added as part of the changes for OPENAM-7584 so possible it was just fixed as well as part of that as a side issue https://stash.forgerock.org/projects/OPENAM/repos/openam/commits/5b7e464b03da1828728af970637519f52bb39b02#openam-ui/openam-ui-ria/src/resources/locales/en/translation.json but this has not been backported to 6.5.2.x branches due to the changes drastically changing existing behaviour.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adam.heath Adam Heath
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: