Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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/freeipa/ticket/3299
The client currently uses XML-RPC. A XML-RPC error can contain nothing but an error code and a message. This prevents us from adding any additional information like the error's class name, warnings, log messages, or extra instructions on how to solve the error. This is limiting us now (see a workaround for instructions in commit 88262a75, or XML-RPC discussion http://www.redhat.com/archives/freeipa-devel/2012-October/msg00535.html), and will probably continue limiting us in the future.
The JSON format is much more flexible. (It's also a more modern standard.)
We should switch to JSON-RPC on the client now, and start deprecating XML-RPC, so that we can drop it in IPA 4.0+.
JSON is used in the Web UI, so support is already there, we just need to switch backends. Our tests use XML-RPC, so that path would still be fully tested for the sake of backwards compatibility.