Bug 1376564 - [RFE] IPA CA issues certificates for non-IPA users
Summary: [RFE] IPA CA issues certificates for non-IPA users
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.3
Assignee: Thomas Woerner
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 18:05 UTC by Roshni
Modified: 2020-07-09 12:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-09 12:47:59 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Roshni 2016-09-15 18:05:14 UTC
Description of problem:
IPA should support certificates to be issued for non-IPA users like AD users

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
[root@auto-hv-02-guest07 ~]# ipa cert-request card1.req
Principal: scuser1
ipa: ERROR: The realm for the principal does not match the realm for this IPA server

Actual results:


Expected results:


Additional info:

Comment 2 Petr Vobornik 2016-09-23 17:01:49 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6356

Comment 5 Amy Farley 2019-08-16 14:04:58 UTC
Moving to RHEL 8 to be considered with some of the other pki work.

Comment 7 Petr Čech 2020-07-09 12:47:59 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. It was unfortunately not given priority Red Hat Enterprise Linux.
Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.
To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you.


Note You need to log in before you can comment on or make changes to this bug.