Cloning Dogtag 10.1.x to 10.2.0 failed due to changes in the JSON format of the security domain info (the XML format does not change). See http://www.redhat.com/archives/freeipa-users/2015-January/msg00031.html.
In Dogtag 10.1.x the SecurityDomainService returns the following JSON structure:
{ "DomainInfo": { "@id": "EXAMPLE", "Subsystem": { "@id": "CA", "Host": { "@id": "CA master.example.com 8443", "Clone": "FALSE", "DomainManager": "TRUE", "Hostname": "master.example.com", "Port": 8080, "SecureAdminPort": 8443, "SecureAgentPort": 8443, "SecureEEClientAuthPort": 8443, "SecurePort": 8443, "SubsystemName": "CA master.example.com 8443" } } } }
In Dogtag 10.2.0 the format has changed to:
{ "id": "EXAMPLE", "Subsystem": [ { "id": "CA", "Host": [ { "id": "CA master.example.com 8443", "Hostname": "master.example.com", "Port": "8080", "SecurePort": "8443", "SecureEEClientAuthPort": "8443", "SecureAgentPort": "8443", "SecureAdminPort": "8443", "Clone": "FALSE", "SubsystemName": "CA master.example.com 8443", "DomainManager": "TRUE" } ] } ] }
The Dogtag client library in the newer version should be able to handle both the old and the new formats, ideally using API versioning. See SecurityDomainClient.get_security_domain_info() in pki/system.py.
Proposed milestone: 10.2.0-x (needed in F21)
Created 10.2.0 Milestone.
Per discussions in IRC, moved this ticket to this milestone where package(s) will need to be re-spun for 10.2.0 on Fedora 21.
NOTE: The fix will need to be ported to later versions of 10.2.X and master, as well.
pki-edewata-0540-Fixed-problem-cloning-Dogtag-10.1.x-to-10.2.x.patch pki-edewata-0540-Fixed-problem-cloning-Dogtag-10.1.x-to-10.2.x.patch
Fixed in:
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2.0
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/1797
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.