Re: [Freeipa-users] JSON-RPC documentation?

2013-01-15 Thread Petr Viktorin
Hello Brian, On 01/15/2013 03:55 AM, Brian Smith wrote: That helps a lot. Thanks! I would use ipalib, but I'm developing a Rails application, so the JSON interface is the quickest (and since XML may be deprecated) While XML may be deprecated, it'll stick around for a long time. But JSON is

Re: [Freeipa-users] JSON-RPC documentation?

2013-01-15 Thread Petr Vobornik
Spying Web UI might be another way how to learn the API. Web UI uses JSON interface for everything it does. You can open developer tools in Chrome (hit F12) and watch communication (network tab). Do something and then look for requests named 'json' a inspect the request payload. To inspect

Re: [Freeipa-users] JSON-RPC documentation?

2013-01-15 Thread Brian Smith
These posts have all been really helpful (especially -vv... its mostly trivial to translate to JSON from the XML). Thanks a lot for the suggestions! I do have one question that might be a new thread, but for me its related. I've added a service account user to the passSyncManagersDNs

Re: [Freeipa-users] JSON-RPC documentation?

2013-01-14 Thread Dmitri Pal
On 01/14/2013 08:16 PM, Brian Smith wrote: Before I pester the dev list, I was wondering if anyone here could point me to documentation on the JSON-RPC interface to FreeIPA. I'm not doing anything fancy, just adding users and updating passwords, so my requirements are pretty tame. I've gone

Re: [Freeipa-users] JSON-RPC documentation?

2013-01-14 Thread Rob Crittenden
Dmitri Pal wrote: On 01/14/2013 08:16 PM, Brian Smith wrote: Before I pester the dev list, I was wondering if anyone here could point me to documentation on the JSON-RPC interface to FreeIPA. I'm not doing anything fancy, just adding users and updating passwords, so my requirements are pretty

Re: [Freeipa-users] JSON-RPC documentation?

2013-01-14 Thread Brian Smith
That helps a lot. Thanks! I would use ipalib, but I'm developing a Rails application, so the JSON interface is the quickest (and since XML may be deprecated) best way forward (unless you know a way to use it in Ruby :). I'm guessing in JSON, the structure would look something like this: {