Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CA Agent certificate list is not sorted by serial number in migration case #2550

Closed
pki-bot opened this issue Oct 3, 2020 · 2 comments
Closed
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

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.

@pki-bot pki-bot added this to the 10.3.5 milestone Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from jmagne (@jmagne) at 2016-08-05 20:13:06

Checked fix into master, closing:

commit f0b1854
Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com
Date: Wed Aug 3 18:01:23 2016 -0700

Fix to sort the output of a cert search by serialno.

@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from jmagne (@jmagne) at 2017-02-27 14:08:12

Metadata Update from @jmagne:

  • Issue set to the milestone: 10.3.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant