You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a migration of cert data is done from one version of cert system to the
latest version of cert system on el7, the cert objects can be written to the
ldap store in an unpredictable order.
Consequently, the agent GUI interface has a couple of places where the user can
search for a list of certs based on a set of search terms.
In the non migration case, it turns out that the user will see any returned
list in serial number order. This is basically the accidental side effect of
having each cert added to the ldap store in order of creation.
The migration case allows no such convenient scenario and the migrated certs
are added in random order.
Since the current search mechanism places no sorting constraints upon the
search, the list can come up in unexpected order.
We need a simple bit of code to make sure the ldap server searches the data
with sorting by serial number in mind.
The text was updated successfully, but these errors were encountered:
This issue was migrated from Pagure Issue #2430. Originally filed by jmagne (@jmagne) on 2016-08-05 20:06:11:
When a migration of cert data is done from one version of cert system to the
latest version of cert system on el7, the cert objects can be written to the
ldap store in an unpredictable order.
Consequently, the agent GUI interface has a couple of places where the user can
search for a list of certs based on a set of search terms.
In the non migration case, it turns out that the user will see any returned
list in serial number order. This is basically the accidental side effect of
having each cert added to the ldap store in order of creation.
The migration case allows no such convenient scenario and the migrated certs
are added in random order.
Since the current search mechanism places no sorting constraints upon the
search, the list can come up in unexpected order.
We need a simple bit of code to make sure the ldap server searches the data
with sorting by serial number in mind.
The text was updated successfully, but these errors were encountered: