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

infotext for Agent property 'User ID Parameter Type' is inaccurate

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Not a defect
    • Affects Version/s: 13.0.0, 13.5.0, 13.5.1, 13.5.2, 14.0.0, 14.1.0, 14.1.1, 14.5.0, 14.5.1, 5.5.1, 14.1.1.1, 14.1.1.2, 14.1.1.3, 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 14.1.1.4, 6.0.0.5, 14.1.1.5, 14.1.2.2, 6.5.0, 6.0.0.6, 6.5.0.1, 6.0.0.7, 14.1.2.3, 6.5.1, 6.5.0.2, 14.1.2.4, 6.5.2
    • Fix Version/s: None
    • Component/s: console
    • Labels:
    • Sprint:
      AM Sustaining Sprint 66
    • Story Points:
      1
    • Needs backport:
      No
    • Support Ticket IDs:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      Infotext for 'User ID Parameter Type' mentions LDAP ... that's legacy from Directory Server Access Management Edition

      How to reproduce the issue

      1. Configure AM
      2. Create Web Agent profile
      3. Select Web Agent profile and go to tab 'AM services'
      4. Click the 'i' link for property 'User ID Parameter Type'
      Expected behaviour
      Text should show 'User ID can be fetched from either SESSION and user identity subject attributes.'
      
      Current behaviour
      Text 'User ID can be fetched from either SESSION and LDAP attributes. ' is shown.
      

      Work around

      OPTIONAL - If you have a workaround, please put the details here (remove this text)

        Attachments

          Activity

            People

            • Assignee:
              lawrence.yarham Lawrence Yarham
              Reporter:
              bthalmayr Bernhard Thalmayr
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: