The profile input ID is only used internally by the server. Clients do not need it, so it should be removed from the CLI output and the REST interface:
$ pki ca-cert-request-profile-show caUserCert -------------------------------------------- Enrollment Template for Profile "caUserCert" -------------------------------------------- Profile ID: caUserCert Renewal: false Input ID: i1 Name: Key Generation Class: keyGenInputImpl Attribute Name: cert_request_type Attribute Description: Key Generation Request Type Attribute Syntax: keygen_request_type Attribute Name: cert_request Attribute Description: Key Generation Request Attribute Syntax: keygen_request ...
Clients can access the inputs using the input name instead of input ID:
CertEnrollmentRequest request = certClient.getEnrollmentTemplate("caUserCert"); ProfileInput kg = request.getInput("Key Generation"); ProfileAttribute typeAttr = kg.getAttribute("cert_request_type"); typeAttr.setValue(type);
In 10.2.x the CLI can be modified to hide the input ID. In 10.3 the REST interface can be modified to remove the input ID.
Alternatively, the input ID can be renamed into something that are less cryptic. This way the input name can become a translatable label. This will require an upgrade script to rename all input IDs in the existing installations. This option is more programmer-friendly.
ProfileInput kg = request.getInputByID("key_generation");
Per Dogtag 10.2.3 Triage meeting of 09/24/2014 - proposed Milestone: 10.2.1
master: 93a8a1f66b401d6a8f46a14d1143feb1ade21de9
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2.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/1710
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.
Login to comment on this ticket.