Upon trying to get an Directory Authenticated EC user cert using the chrome browser you end up with the error:
Sorry, your request is not submitted. The reason is "Certificate Request Not Found".
Reproduction: https://our_corporate_rhcs_ca:8443/ca/ee/ca/profileSelect?profileId=caECDirUserCert
Happened to me on Chrome Version 49.0.2623.87 (64-bit) in Fedora 23 but I suspect the Browser as a whole either doesn't know how to EC CSR or at least doesn't know how or that it should do such things on the RHCS pages.
Internally we are probably OK with RHCS detecting if people are using chrome or anything other than FF and telling them to use FF instead. But it would be really nice if chrome was fully supported.
Per Bug Triage of 05/03/2016: 10.3.0
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1301755 (Red Hat Certificate System)
NOTE: If only a portion of this bug is fixed in 10.3.0 (e. g. - browser detection), file a 10.3.0 bug for that, and move this bug to 10.4.
Associated with PKI TRAC Ticket #1245 - RFE: Importing client certificate in Chrome fails
Useful URL to determine what a browser supports:
Replying to [comment:4 mharmsen]:
Detection only patch checked into master:
Moved bug to 10.4.
Metadata Update from @dminnich: - Issue assigned to mharmsen - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.4 (was: UNTRIAGED)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.4)
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/2426
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)
Login to comment on this ticket.