RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1282

If the IPA proxy configuration is missing, the installation wizard will generate a cryptic message about XML parsing error:

{{{
[30/Jan/2015:00:05:04][http-9445-1]: WizardPanelBase: pingCS: parser
failedorg.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 50;
White spaces are required between publicId and systemId.
}}}

The installation wizard probably should have checked the HTTP error code before parsing the response data, so a missing proxy problem could be handled in a better way. Also, if the XML parsing failed, the data being parsed should be displayed so it can be troubleshot.

See the following threads:
* https://www.redhat.com/archives/freeipa-users/2015-January/msg00352.html
* https://www.redhat.com/archives/freeipa-users/2015-February/msg00041.html

See also error reporting improvement for Dogtag 10 in ticket #942.

Proposed milestone: 9.0.x

Per discussions in the RHEL 7.3 Triage meeting of 01/06/2016: priority low

* check to see if this issue is already corrected in Dogtag 10
* remove the proxy configuration file in order to test for the message

This error has only popped up in Dogtag 9.  It does not apply to RHEL 7.x, which uses Dogtag 10.x.  Closing as NOTABUG.