[OPENAM-5867] Data Store LDAP server (admin-ordered) list is reordered by OpenAM Created: 21/Apr/15  Updated: 11/May/20  Resolved: 08/Jan/19

Status: Resolved
Project: OpenAM
Component/s: console, ssoadm
Affects Version/s: 11.0.0, 11.0.1, 11.0.2, 11.0.3, 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 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, 6.0.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.5.0, 6.0.0.6, 6.0.0.7
Fix Version/s: 13.5.3, 14.1.2, 6.5.1, 6.0.1, 5.5.2, 7.0.0

Type: Bug Priority: Major
Reporter: hadi hahmadi Assignee: Sachiko Wallace
Resolution: Fixed Votes: 2
Labels: Backlog, EDISON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04 64 -bit, OpenAM 12.0.0, OpenDJ 2.6,


Issue Links:
Backport
is backported by OPENAM-15711 Backport OPENAM-5867: Data Store LDAP... Closed
Duplicate
is duplicated by OPENAM-13185 OpenAM data Sources Order of Preceden... Closed
Regression
caused OPENAM-16036 Identity stores configuration broken ... Resolved
Relates
relates to OPENAM-16222 LDAP decision node's server list gets... Open
Target Version/s:
Sprint: AM Sustaining Sprint 58, AM Sustaining Sprint 59
Story Points: 5
Needs backport:
No
Support Ticket IDs:
Verified Version/s:
Needs QA verification:
Yes
Functional tests:
No
Are the reproduction steps defined?:
Yes and I used the same an in the description

 Description   

DataStore HA and load-balancing can be provided by adding multiple LDAP servers to the DataStore configuration. As documentation promises, ordering the list of LDAP servers is important.

For a site configuration (ID 02) with two servers (IDs 01 and 03). Got to a DataStore configuration and under LDAP servers, add the following four values in the following order:
zzz.example.com:1389|01|02
xxx.example.com:1389|01|02
zzz.example.com:1389|03|02
xxx.example.com:1389|03|02
Save the configuration, and go back to the page (refreshed). List is reordered as
xxx.example.com:1389|01|02
xxx.example.com:1389|03|02
zzz.example.com:1389|03|02
zzz.example.com:1389|01|02

Same happens when configuration is imported via ssoadm tool or jsp.



 Comments   
Comment by Peter Major [X] (Inactive) [ 03/Aug/16 ]

I believe this should be addressed in a major version as it will have upgrade implications.

Comment by Simon Moffatt [ 31/Mar/17 ]

As a workaround couldn't external DNS mapping be used? For example it seems the re-order is being done alphabetically. For example, make entries such as a.example.com, b.example.com so they order correctly within OpenAM. Outside of OpenAM add DNS CNAME entries to take a.example.com to the actual server.

Comment by Ľubomír Mlích [ 18/Mar/19 ]

Reproduced in 6.5.0

Verified as fixed in ForgeRock Access Management 6.5.1-M3 Build 9264f9957e (2019-March-11 10:19) 

Generated at Wed Sep 30 02:58:52 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.