RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The sss-certmap man page could use a statement in the priority section mentioning that processing stops when a matched rule is found and no further rules are checked.

Version-Release number of selected component (if applicable):
sssd-1.15.2-43.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. man sss-certmap

Actual results:

   PRIORITY
       The rules are process by priority while the number '0' (zero) indicates the highest priority.
       The higher the number the lower is the priority. A missing value indicates the lowest
       priority.

       Internally the priority is treated as unsigned 32bit integer, using a priority value larger
       than 4294967295 will cause an error.


Expected results:

A note about processing stopping after a match would be helpful.

Additional info:

Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3469

* master: 56839605d139573319b7df24774b56ea78ec742b

Verified.

Version ::

sssd-1.16.0-25.el7.x86_64
libsss_certmap-1.16.0-25.el7.x86_64

Results ::



   PRIORITY
       The rules are processed by priority while the number '0' (zero) indicates the highest
       priority. The higher the number the lower is the priority. A missing value indicates the
       lowest priority. The rules processing is stopped when a matched rule is found and no further
       rules are checked.

I can see the note about processing stopped in the newer version.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3158