As a Developer of a Product, I want to call a specific version of API call, without being affected by higher or lower version of the IdM server than my testing instance so that the Product is not dependent on a specific IdM server version and respective changes Version-Release number of selected component (if applicable): 4.2 How reproducible: always Steps to Reproduce: 1. run any 'ipa' command from client newer than an IPA server. E.g. user-find Actual results: There is only "one" API, API version is used only for rejecting request and not managing requests. Expected results: Client can call API with API version specified. Server will respond according to the specified version(different output/required params, etc.). The supported versions are yet to be determined.
Possibly related upstream tickets: * https://fedorahosted.org/freeipa/ticket/33 * https://fedorahosted.org/freeipa/ticket/2026 * https://fedorahosted.org/freeipa/ticket/4427
Upstream ticket: https://fedorahosted.org/freeipa/ticket/4427
master: https://fedorahosted.org/freeipa/changeset/9a21964877c4bb64599e75ca708ec83a72abeb51 https://fedorahosted.org/freeipa/changeset/79d1f5833547044a7cb2700454cacb2a0976dd5f https://fedorahosted.org/freeipa/changeset/4284d4fb4da1049c8b9f23d838f963b301aef97d https://fedorahosted.org/freeipa/changeset/8466e9444085fbd06a2496e8b83e28102b263e47 https://fedorahosted.org/freeipa/changeset/5f52e0fcbfb927c3adada58e94bd10685535d2bd
Created attachment 1191258 [details] tkt_4427.log Verified using IPA version :: ipa-server-4.4.0-7.el7.x86_64 Marking RFE BZ as verified. There is a BZ1357488 opened which is related to this RFE.
This Bugzilla is being repurposed, to track global availability of the IdM Server API (as a Tech Preview). This is the more general user story proposed for that purpose: As a Developer, I want to communicate with IdM Server via stable API and without being affected by higher or lower version of the IdM server than my testing instance, so that the API call is not broken when used with different IdM servers. This change in focus does not need any actual code changes, it is rather about making the support level of the IdM Server API explicit, tracked and reference-able in other bugs. Please note, that the actual IdM Server API functionality is composed from several parts: * IdM Server JSON-RPC API itself, as it was available since RHEL 7.0 (unsupported at all, available as Tech Preview since RHEL-7.3) * IdM Server API browser (announced as Experimental in RHEL-7.2 in Bug 846033, moved to Tech Preview in RHEL-7.3 in Bug 1335567) * IdM Server API documentation and guidance (based on https://vda.li/en/posts/2015/05/28/talking-to-freeipa-api-with-sessions/, DOC Bugzilla TBD).
(In reply to Martin Kosek from comment #13) > * IdM Server JSON-RPC API itself, as it was available since RHEL 7.0 > (unsupported at all, available as Tech Preview since RHEL-7.3) This is the part covered by this bug, including API versioning which was a prerequisite for productizing IdM Server API.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2404.html