<XMLResponse> <DomainInfo> <?xml version="1.0" encoding="UTF-8" standalone="no"?> <DomainInfo> <Name>IPA</Name> <CAList> <CA><Host>vm-093.idm.lab.bos.redhat.com</Host> <UnSecurePort>80</UnSecurePort> <SecurePort>443</SecurePort> <SecureEEClientAuthPort>443</SecureEEClientAuthPort> <SecureAgentPort>443</SecureAgentPort> <SecureAdminPort>443</SecureAdminPort> <Clone>FALSE</Clone> <SubsystemName>CA vm-093.idm.lab.bos.redhat.com 8443</SubsystemName> <DomainManager>TRUE</DomainManager> </CA> <SubsystemCount>1</SubsystemCount> </CAList> <KRAList><SubsystemCount>0</SubsystemCount></KRAList> <OCSPList><SubsystemCount>0</SubsystemCount></OCSPList> <TKSList><SubsystemCount>0</SubsystemCount></TKSList> <RAList><SubsystemCount>0</SubsystemCount></RAList> <TPSList><SubsystemCount>0</SubsystemCount></TPSList> </DomainInfo> </DomainInfo> <Status>0</Status> </XMLResponse>
Notice the DomainInfo XML fragment within the DomainInfo element. This is easy enough to fix -- and most likely its only a problem on the old interfaces - a problem that was introduced when the SecurityDomainProcessor was introduced, but we will need to check all the places it is used, and make sure they still work.
Metadata Update from @vakwetu: - Issue set to the milestone: UNTRIAGED
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/1181
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.