We need proper default subjectDN for CMC request authenticated through SharedToken.
Metadata Update from @cfu: - 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 set to the milestone: 10.5
Metadata Update from @cfu: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1592961
Metadata Update from @cfu: - Issue assigned to cfu
commit 2746c4f70d738266b72161d80c1a2ff6a9a45391 (HEAD -> master, origin/master, origin/HEAD, ticket-3037-SharedTokenSbjdn-A-master) Author: Christina Fu cfu@redhat.com Date: Tue Jun 19 15:21:54 2018 -0700
Ticket 3037 CMC SharedToken SubjectDN default This patch adds proper subjectDN to CMC requests authenticated via ShardToken. Specifically, the AuthTokenSubjectNameDefault profile default is added to the default CMC profiles that authenticates via SharedToken. Code were added to ensure that the proper subjectDN retrieved from the mapped user entry is added to the AuthToken for such utilization. Fixes https://pagure.io/dogtagpki/issue/3037 Change-Id: Id92d9496ab5b41ea7b5dcffb8d73d3ffe8b29fbc
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.10-1.fc27 - Issue set to the milestone: 10.5.10 (was: 10.5)
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/3155
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.