#2447 CertRequestInfo has incorrect URLs
Closed: Fixed None Opened 7 years ago by ftweedal.

The CertRequestInfos in the enrollment response contains invalid URLs:

{"total":1
,"entries":[
  {"requestType":"enrollment"
  ,"requestStatus":"complete"
  ,"requestURL":"https://f24b-0.ipa.local:8443/ca/rest/50"
  ,"certId":"0x2d"
  ,"certURL":"https://f24b-0.ipa.local:8443/ca/rest/45"
  ,"certRequestType":"pkcs10"
  ,"operationResult":"success"
  }
 ]
,"Link":[]
}

Also occurs for GET /ca/rest/certrequests/<id>.
Maybe occurs in other places too?

Per PKI Bug Council of 08/31/2016: 10.3.6

alee@aleeredhat pki]$ git push origin master
Counting objects: 36, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (27/27), done.
Writing objects: 100% (36/36), 3.00 KiB | 0 bytes/s, done.
Total 36 (delta 21), reused 0 (delta 0)
To ssh://vakwetu@git.fedorahosted.org/git/pki.git
bc65e12..7a93dbe master -> master

Checked into master:
7a93dbeae18407e28437f4affc31ddc24a2c42f2

Cherry-picked into DOGTAG_10_3_BRANCH:

From 7baa7e60b708c5b4c79d6dd963321d34958cc81b Mon Sep 17 00:00:00 2001
From: Ade Lee alee@redhat.com
Date: Fri, 2 Sep 2016 16:08:02 -0400
Subject: [PATCH 04/10] Fix CertRequestInfo URLs

The URLs were generated by a UriBuilder that referred to the resource's
annotated path. This top-level path changed though, even if the underlying
paths did not. Replace this with a reference to the getX methods instead.

Also fixed a few eclipse flagged warnings (unused imports etc).

Ticket 2447

(cherry picked from commit 7a93dbeae18407e28437f4affc31ddc24a2c42f2)

Metadata Update from @ftweedal:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.3.6

7 years ago

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/2567

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.

Login to comment on this ticket.

Metadata