dogtagpki

#287 Improvements for URI matcher
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

The PKIRealm uses a URI matcher to match the incoming request URI with the mappings defined in auth.properties in order to determine the ACI of the resource being accessed.

The current URI matcher implementation has some limitations:

  • It doesn't support wildcards, so it's not possible to match pattern such as "/certrequests/{id}/approve".
  • It will return the first match, which may not necessarily be the longest match. For example /a/b/c may match /a first, but the best match should have been /a/b.

Once this is fixed, the ACI should be fixed to support more granular access controls for different methods in the same resource. For example:

  • /kra/rest/keyrequests/{id}/
  • /kra/rest/keyrequests/archive
  • /kra/rest/keyrequests/recover

Another option is to use roles as described in ticket #258 and method-level access control using RESTEasy.

master:

  • cb209df95c4dee11f2a912e20b417fa3bc41c88f

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.0.1

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/858

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Normal
defect
Auth
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.