The CA request pages show boxes like
Request Information Request ID: 83 Request Type: enrollment Request Status: pending Requestor Host: 10.64.40.177 Assigned To: Creation Time: Wed Oct 21 06:44:58 UTC 2015 Modification Time: Wed Oct 21 06:44:58 UTC 2015
Certificate Profile Information Certificate Profile Id: caServerCert Approved By: admin Certificate Profile Name: Manual Server Certificate Enrollment Certificate Profile Description: This certificate profile is for enrolling server certificates.
An RFE was recently worked to include a link on the cert in the agent gui to a page that contains those same request boxes. We did this so we could gather more info about a certs origin, in particular the person who requested it. This works well, but if people don't fill in the Requestor Name field in the profile the info is understandingly blank.
LDAP contains all kinds of tasty info about these original request, especially if dir based auth was used.
dn: cn=9970005,ou=ca,ou=requests,o=ca extdata-auth--005ftoken--002euid--005b0--005d: dminnich extdata-auth--005ftoken--002euserdn: uid=dminnich,ou=users extdata-authenticatedname: uid=dminnich,ou=users,dc=redhat,dc=com extdata-auth--005ftoken--002email--005b0--005d: whatever@redhat.com extdata-auth--005ftoken--002egroups--005b0--005d: cn=directory administrators, extdata-auth--005ftoken--002euserid: dminnich
Could we expose some of this stuff in the request pages as well? In particular I'm interested in uid/userid/userdn/authenticatedname. Any of those would work. Don't know what we might need in the future though. Clicking a button and seeing all the things even it was just an ugly text dump might be useful.
Per CS/DS meeting of 11/02/2015: 10.4 - trivial
Metadata Update from @dminnich: - 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/2238
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)