While issuing a CA cert, Path Length constraint accept only -1 value.
-1
1) Spawn CA 2) Submit certificate request pki -c Secret.123 client-cert-request "cn=test" --profile caCACert 3) As agent, update the above request to specify the pathLen constraint :
pki -c Secret.123 client-cert-request "cn=test" --profile caCACert
# pki -d ~/.dogtag/pki-tomcat/ca/alias/ -n caadmin -c Secret.123 ca-cert-request-review 41 --file ca-cert-pathlen.crt # vi ca-cert-pathlen.crt # cat ca-cert-pathlen.crt ~snip~ <policyAttribute name="basicConstraintsPathLen"> <Value>10</Value> <Descriptor> <Syntax>integer</Syntax> <Description>Path Length</Description> <DefaultValue>-1</DefaultValue> </Descriptor> </policyAttribute> ~snip~
4) Approve or update request
# pki -d ~/.dogtag/pki-tomcat/ca/alias/ -n caadmin -c Secret.123 ca-cert-request-approve 41 --input-file ca-cert-pathlen.crt BadRequestException: Request Max Path Length not matched Rejected - {1} # pki -d ~/.dogtag/pki-tomcat/ca/alias/ -n caadmin -c Secret.123 ca-cert-request-update 41 --input-file ca-cert-pathlen.crt BadRequestException: Request Max Path Length not matched Rejected - {1}
PS: The same behavior is observed when updating/approving request via web UI
NOTE: The following constraint message is displayed on both Web UI and CLI
This constraint accepts the Basic Constraint extension, if present, only when Criticality=true, Is CA=true, Min Path Length=-1, Max Path Length=-1
This seems to be working correctly after setting a positive value in CS.cfg..
positive
However, -1 "logically" refers to unlimited but, the system does not accept a positive value. Since there is a workaround, lowering the priority
Metadata Update from @dmoluguw: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: minor
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/3296
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.