Adding the Docusign AccountManagement API

[bvandenbos]

Not sure if you want to take this, but I've added the AccountManagement API. There's a bit of a catch. Docusign requires custom HTTP Headers for authentication for the AccountManagement API and soap4r doesn't give you access to HTTP headers. So, to actually use the AccoutManagement API (in my fork), you have to monkey patch soap4r to set the headers... which sucks. Maybe you know of a way around that.

Thanks for the Gem!

Cheers,

ben

Also, note I bumped the version, which you will probably want to change.

[texel]

Cool, thanks! So, soap4r does let you define header handlers for things like authentication. Take a look at https://github.com/texel/docusign/blob/master/lib/docusign/base.rb#L24-37 and both https://github.com/texel/docusign/blob/master/lib/docusign/auth_header_handler.rb and https://github.com/texel/docusign/blob/master/lib/docusign/integrators_key_auth_header_handler.rb for examples.

Also, I'm not maintaining this anymore, so I can peruse your changes, and perhaps merge it in, but would have to check w/ the Docusign team... would you potentially be interested in taking over development of the canonical gem?

[bvandenbos]

Unless I'm mistaken, those are soap auth headers, not http headers.

I'm not against it taking it over. Is Docusign actively involved in
this at all?

On Jan 21, 2012, at 10:30 PM, Leigh Caplan
[email protected]
wrote:

Cool, thanks! So, soap4r does let you define header handlers for things like authentication. Take a look at https://github.com/texel/docusign/blob/master/lib/docusign/base.rb#L24-37 and both https://github.com/texel/docusign/blob/master/lib/docusign/auth_header_handler.rb and https://github.com/texel/docusign/blob/master/lib/docusign/integrators_key_auth_header_handler.rb for examples.

Also, I'm not maintaining this anymore, so I can peruse your changes, and perhaps merge it in, but would have to check w/ the Docusign team... would you potentially be interested in taking over development of the canonical gem?

---

Reply to this email directly or view it on GitHub:
#5 (comment)