Ruby on Rails DocuSignSample

[schleg]

I'm trying to get the sample RoR app to run. I entered my credentials in the docusign.yml file, started the server, and out-of-the-box I get 

OpenSSL::X509::StoreError in LoginsController#new
system lib
Rails.root: /Volumes/SugarPod/Dropbox/source/DocuSign-eSignature-SDK/Ruby/DocuSignSample
Application Trace | Framework Trace | Full Trace
app/controllers/logins_controller.rb:30:in `new'

I'm using Ruby 1.8.7 and Rails 3.0.4

Anything obvious I should look at first?

[nicholasareed · Accepted solution]

Yes, if you look at the

/config/initializers/docusign.rb

 you'll need to change lines

Docusign::Config[:ca_file] = '/usr/lib/ssl/certs/ca-certificates.crt'

 to reflect where your CA file is stored. 

[schleg]

Thanks, that was the ticket! For future reference (for anyone with this same issue) I had to create an SSL cert with openssl on Mac OSX like this--

sudo openssl req -out CSR.csr -new -newkey rsa:2048 -nodes -keyout privateKey.key 

sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout privateKey.key -out ca-certificates.crt

I had to sudo create the path /usr/lib/ssl/certs

Anyway, works now. Looking forward to checking it out.

[nickhammond]

I've added this to my config/initializers/docusign.rb file but it doesn't seem to be loading in that configuration because I'm still getting the certificate verify failed. I have a ca-certificates file that it's pointing to and am using for another connection, what does your connection function look like? Is the Docusign::Config[:ca_file] value used anywhere besides setting it in that initializer?

[nickhammond]

I can see that the Docusign::Config hash has everything in there properly just not following where it gets passed over to soap4r. Any tips?

[schleg]

Here's my docusign.rb initializer--

require 'docusign'

Docusign::Config = HashWithIndifferentAccess.new(YAML.load_file("#{Rails.root}/config/docusign.yml")[Rails.env])

Docusign::Config[:verify_mode] = OpenSSL::SSL::VERIFY_PEER Docusign::Config[:ca_file] = '/usr/lib/ssl/certs/ca-certificates.crt'

although I don't think I had to change that. Once I added the cert file I could just run the Rails app as expected. In docusign.yml make sure you are using your email address for the user_name valuep.

[nickhammond]

Thanks for the reply, this issue has been driving me crazy. My docusign.rb initializer looks the same I'm just not seeing where the docusign gem actually picks up or uses that information, does it need to be in the connection somewhere? Is there another method that utilizes the ca_path? It's strange because open-uri picks up on my ca certificates file without pointing it somewhere but I know that's part of the problem with soap4r.

Gems:

soap4r-1.5.8

docusign-0.8.0

  def docusign_connection
    @docusign_connection ||= Docusign::Base.login(
      :integrators_key => Docusign::Config[:integrator_key],
      :email => current_account.docusign_username,
      :password     => current_account.docusign_password,
      :endpoint_url =>Docusign::Config[:default_endpoint_url],
      :wiredump_dev => STDOUT
    )
  end

[nicholasareed]

You need the docusignsdk gem instead of docusign. We modified the old docusign gem to include the ca_cert configuration (so that it can run on Heroku). 

[nickhammond]

Great, thank you! I'll try that out today. I saw the docusignsdk gem in a couple articles but it was unclear if that was just renamed to the docusign gem since all of the github pages and everything 404. Any plans on getting this added into the official docusign gem?  Accepting pull requests?

[nicholasareed]

Definitely accepting pull requests! The current docusignsdk gem is at https://github.com/nicholasareed/docusignsdk