Currently the operations to manage certificates are handled by separate REST resources which are more RPC-like. They should be combined into a single resource which is the certificates itself. This way the URL will not change suppose the operations change in the future.
Here is the current interface:
public interface CertResource { @POST @Path("agent/certs/{id}/revoke-ca") public CertRequestInfo revokeCACert(@PathParam("id") CertId id, CertRevokeRequest request); @POST @Path("agent/certs/{id}/revoke") public CertRequestInfo revokeCert(@PathParam("id") CertId id, CertRevokeRequest request); @POST @Path("agent/certs/{id}/unrevoke") public CertRequestInfo unrevokeCert(@PathParam("id") CertId id, CertUnrevokeRequest request); }
Proposed interface:
public interface CertResource { @POST @Path("agent/certs/{id}") public CertRequestInfo processCert(@PathParam("id") CertId id, @QueryParam("action") String action, CertRevokeRequest request); }
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
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/1248
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)