Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security Certificate Issue #98

Open
agrover8 opened this issue Mar 7, 2016 · 6 comments
Open

Security Certificate Issue #98

agrover8 opened this issue Mar 7, 2016 · 6 comments

Comments

@agrover8
Copy link

agrover8 commented Mar 7, 2016

Hi,
I am getting Uncaught AssertionError: expected [Error: self signed certificate] to equal error in ABAO as my API's is using secured certificate. Is there any way in ABAO if I can pass the security certificate file?

@plroebuck
Copy link
Collaborator

How would you define your test if all you had was curl?
If you can describe your use-case, maybe I can come up with something...
Otherwise, wondering if this isn't something you can already do with HTTP headers...

@itafroma
Copy link

Hi @plroebuck, one use case for this is running Abao on a local development environment, where you may need to use a self-signed certificate for logistical reasons or convenience. If I had to define the test via cURL, I'd use its -k/--insecure insecure option on the command line or set the CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST options to 0 if I were using libcurl.

@plroebuck
Copy link
Collaborator

plroebuck commented Jun 18, 2016

If the idea is to do insecure testing, would this work?

$ env NODE_TLS_REJECT_UNAUTHORIZED=0 abao api.raml --server localhost:8181

@itafroma
Copy link

That totally works, thanks!

@plroebuck
Copy link
Collaborator

@agrover8, does the workaround above address your issue? Still need a real longterm solution, but we can document this as stand-in procedure until then...

@gbarker
Copy link

gbarker commented Sep 9, 2016

@plroebuck the use case is one where the server is secured using Mutual TLS. So a specific cert needs to be passed by the client. Curl handles it with the --cert option. Here is a description of how it works with curl: http://callistaenterprise.se/blogg/teknik/2011/04/04/curl-mutual-authentication-and-web-services/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants