Bug 916289 - IPA should own its certificate profile
Summary: IPA should own its certificate profile
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-27 18:19 UTC by Rob Crittenden
Modified: 2015-06-05 17:18 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-01 13:18:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Crittenden 2013-02-27 18:19:59 UTC
Description of problem:

For some reason when we initially added support for pki-core we adding the certificate profile to the pki-ca package.

This has been problematic for both sides, forcing a new release of pki-core whenever IPA needs an update.

We should coordinate moving ownership of this from the pki-core package to the ipa package.

Comment 1 Nathan Kinder 2013-10-10 19:08:12 UTC
Reassigning this to FreeIPA.  The profile needs to be copied into the FreeIPA source tree and the IPA installation scripts need to be updated to copy it into the CA profile directory.  Once this is done, we can remove it from Dogtag.

Comment 2 Martin Kosek 2013-10-29 15:14:24 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4002

Comment 3 Fedora End Of Life 2013-12-21 15:24:53 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Martin Kosek 2014-01-02 13:24:19 UTC
This RFE is still valid for current Fedora version, changing the version field.

Comment 5 Fedora End Of Life 2015-05-29 08:54:23 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Alexander Bokovoy 2015-06-01 13:18:22 UTC
With work done for subCAs in FreeIPA 4.2 this is not applicable anymore.
http://www.freeipa.org/page/V4/Sub-CAs


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