dogtagpki

#1051 allow dogtag internal db tree to be a subtree of an existing tree
Closed: Fixed Opened by vakwetu.

Closed: Fixed
Reopen Issue

Suggested Timeframe: July 10.2

To allow DRM to share the same replication agreement when integrated into IPA, we need to allow the dogtag internaldb tree to be a subtree of an existing tree, rather than requiring it to be its own tree, with its own hierarchy.

This is related to - and in fact extracted from ticket 1045 (top level DN) which will be deferred to a future release.

Per CS/DS meeting of 06/30/2014, proposed Milestone: Dogtag 10.2 (July)

Fixed:

[alee@localhost scripts]$ git push origin master
Counting objects: 247, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (42/42), done.
Writing objects: 100% (69/69), 8.44 KiB | 0 bytes/s, done.
Total 69 (delta 29), reused 0 (delta 0)
To ssh://vakwetu@git.fedorahosted.org/git/pki.git
bebc70b..80c4091 master -> master

Metadata Update from @vakwetu:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.2 - 07/14 (July)

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/1616

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Normal
defect
Installation/Configuration
IPA
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.