PDA

View Full Version : [FIXED] Self-signed Certifcates or our own AD CA?



tangix
11 Apr 2016, 4:35 AM
Hello,
currently evaluating ST (kudoz to Lee Boonstra for a great marketing job at the Sencha Roadshow last Friday in Stockholm!)
We are using our Active Directory infrastructure to generate trusted certificates internally to our various development machines. All Windows clients have the CA Cert installed in their trusted store so Chrome and IE connect just fine in general with no warnings.

The problem is how to configure ST 1.0.1 on Windows to recognize the AD CA cert. I get the following message when trying to run a simple test:

Error: unable to verify the first certificate at Error (native) at TLSSocket.<anonymous> (_tls_wrap.js:1000:38) at emitNone (events.js:67:13) at TLSSocket.emit (events.js:166:7) at TLSSocket._finishInit (_tls_wrap.js:567:8)

Is it possible to get ST to run in this type of situation?

tangix
11 Apr 2016, 6:55 AM
I have tried adding the ENV variable NODE_TLS_REJECT_UNAUTHORIZED as suggested not node.js in many places on the net. Still no go.

tangix
11 Apr 2016, 10:47 PM
No reply from Sencha, so I add my solution. I purchased a RapidSSL certificate for another domain I control and installed it on the development server. Added the hostname and IP to the /etc/hosts file and all is now well.

dongryphon
12 Apr 2016, 3:07 PM
We are looking into some reported SSL/TLS issues - see https://www.sencha.com/forum/showthread.php?308999 for details, but thanks for posting a workaround.

dongryphon
12 Apr 2016, 3:09 PM
I have moved this thread to Bugs forum and opened a new ticket since the other SSL/TLS issue seems resolved.

ttbgwt
18 Apr 2016, 12:54 PM
Just tried running sencha test, works fine for google.com or sencha.com, but when we designate our internal application running on our vpn we see this in the logs. This is a show-stopper for us.

301 2:17:00.535
[INF] Proxy Server open on port 8701
302 2:17:01.148
[ERR] Error: self signed certificate
at Error (native)
at TLSSocket.<anonymous> (_tls_wrap.js:1000:38)
at emitNone (events.js:67:13)
at TLSSocket.emit (events.js:166:7)
at TLSSocket._finishInit (_tls_wrap.js:567:8)
303 2:17:35.140