Node JS -- Public SSL Certs
Hi All,
I'm a n00b when it comes to public SSL CA certs and coding node.js to be an SSL/TLS. I have followed the instructions on this site: http://nodejs.org/api/tls.html I am using the following options to invoke a listener. I followed the instructions and concatenated the network solution certs together. I'm not sure what is right or wrong, but the public cert is not working. Code:
cat FILES_CERTS < All_AddTrust_DV_2_CA.crt Code:
var secure_options = { Server Output: Code:
[2014-11-21 10:18:34.073] [INFO] console - server connected 'unauthorized' Client Request: Code:
openssl s_client -connect 127.0.0.1:46900 |
Ok. I figured it out.
There are a few things wrong with the instructions from everyone that I have seen give out node examples for public CA-signed certs. Again this is for NetworkSolutions as a CA provider. This is as a server CA and NOT a client CA. There is no dual-CA authentication, only the single side from the server. The notes for adding the CA public certs are confusing, because the CA is not the CA attribute in the options. It is the cert attribute. Symptoms for this are no matter what you do the same error appears and you can authenticate it if you use your creds as a part of the call Code:
openssl s_client -CAfile 4_CRTs_Sample_DVServ_DVUser_AddT.crt -connect sample.whataremindsfor.com:56900 Step 1: If you have several crts cat them all together using your full-qualified domain first. Code:
cat SAMPLE.WHATAREMINDSFOR.COM.crt DV_NetworkSolutionsDVServerCA2.crt DV_USERTrustRSACertificationAuthority.crt AddTrustExternalCARoot.crt > 4_CRTs_Sample_DVServ_DVUser_AddT.crt NO: Code:
-----BEGIN CERTIFICATE----------END CERTIFICATE----- Code:
-----BEGIN CERTIFICATE----- Step 3: Don't use the 'ca' attribute for server side CA. Only use the 'cert' attribute. Code:
var secure_options = { |
I apologize if I don't have anything else to add, just wanted to say, Thanks it worked perfectly for me.
|
All times are GMT -5. The time now is 06:23 PM. |