Results 1 to 6 of 6

Thread: Self-signed Certifcates or our own AD CA?

    Success! Looks like we've fixed this one. According to our records the fix was applied for ORION-690 in 1.0.3.76.
  1. #1
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    741

    Default Self-signed Certifcates or our own AD CA?

    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:
    Code:
    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?

  2. #2
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    741

    Default

    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.

  3. #3
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    741

    Default

    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.

  4. #4
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748

    Default

    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.
    Don Griffin

    "Use the source, Luke!"

  5. #5
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748

    Default

    I have moved this thread to Bugs forum and opened a new ticket since the other SSL/TLS issue seems resolved.

  6. #6
    Ext JS Premium Member
    Join Date
    May 2008
    Posts
    431

    Default

    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

Similar Threads

  1. [FIXED] Sencha Architect not Signed
    By DonRul in forum Sencha Architect 2.x: Bugs
    Replies: 1
    Last Post: 12 Nov 2012, 1:21 PM
  2. [FIXED] [3.0.0.181 - Touch 2.1-20121002] iOS build is not signed
    By svenna in forum Sencha Cmd
    Replies: 2
    Last Post: 5 Oct 2012, 10:27 PM
  3. Signed with invalid entitlements
    By pekue in forum Sencha Cmd
    Replies: 4
    Last Post: 21 May 2012, 1:07 PM
  4. Deploy packaged and signed app to the appstore
    By TomGH in forum Community Discussion
    Replies: 3
    Last Post: 15 Mar 2012, 7:00 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •