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

LDAP decision node's server list gets reordered

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 6.0.0, 6.5.0, 7.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Bug description

      Sets do not guarantee order of the data that is in them. For example, the Set  ['first', 'second', 'third'] set in LdapDecisionNode's primaryServers can come back as  ["third", "first", "second"] when returning from the GET call. Lists do respect order however, but there isn't a way from the schema call to differentiate between set and list attributes. We need to either change set attributes as ordered (prefered solution) or to provide feedback in the schema call to denote whether it is a set or list.

      How to reproduce the issue

      1. Create a new LdapDecisionNode

      2. Set the primaryServers value as ["first", "second", "third"].

      3. Save this node.

      Observe the value of primaryServers

      Expected behaviour
      Returned value should still be ["first", "second", "third"]
      
      Current behaviour
      Returned value is ["third", "first", "second"]
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                andrew.hertel Andrew Hertel
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: