Microgateway(version 2.3.0 Beta) config error on Apigee Private Cloud (Version 4.15.07.00)

Not applicable

Here is the configure command I am using for Microgateway to communicate with Apigee Private Cloud.

Please see below error message. After the command execution, I can see two proxies show up on Apigee Edge API Proxies list: "edgemicro_internal" and "edgemicro_auth"

sudo edgemicro private configure -o wag-apigee-stg -e stg1 -u jie.hu@walgreens.com -r https://dlv8-apg04-stg.walgreens.com:9009 -m http://dlv8-apg05-stg.walgreens.com:8080 -v default

current nodejs version is v6.9.1

current edgemicro version is 2.3.0-beta

password:

delete cache config

init config

file doesn't exist, setting up

configuring edgemicro internal proxy

deploying edgemicro internal proxy

deploying edgemicro-auth app

Give me a minute or two... this can take a while...

App edgemicro-auth deployed.

checking org for existing vault

vault already exists in your org

{ Error: Hostname/IP doesn't match certificate's altnames: "Host: dlv8-apg04-stg.walgreens.com. is not in the cert's altnames: DNS:q.wlgrn.com, DNS:services-qa.walgreens.com"

at Object.checkServerIdentity (tls.js:199:17)

at TLSSocket.<anonymous> (_tls_wrap.js:1068:29)

at emitNone (events.js:86:13)

at TLSSocket.emit (events.js:185:7)

at TLSSocket._finishInit (_tls_wrap.js:586:8)

at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)

reason: 'Host: dlv8-apg04-stg.walgreens.com. is not in the cert\'s altnames: DNS:q.wlgrn.com, DNS:services-qa.walgreens.com',

host: 'dlv8-apg04-stg.walgreens.com',

cert:

{ subject:

{ C: 'US',

ST: 'Illinois',

L: 'Deerfield',

O: 'Walgreen Co.',

OU: 'ecomm',

CN: 'services-qa.walgreens.com' },

issuer:

{ C: 'US',

O: 'Symantec Corporation',

OU: 'Symantec Trust Network',

CN: 'Symantec Class 3 Secure Server CA - G4' },

subjectaltname: 'DNS:q.wlgrn.com, DNS:services-qa.walgreens.com',

infoAccess: { 'OCSP - URI': [Object], 'CA Issuers - URI': [Object] },

modulus: 'DF658F66BBA782EBCA19296838FE5E2A3ABEBA11430508DCAA8912C44744AB6DE27FF287384004262413973364BD8F558450498319B94FEE491AF5D39E809C58CE0E9C4716A81341BF5D98642DE7EBB62323957D2CAF04F8ED699AEBFEE549D9DF531226E7E5B187EB176BB9B59AFB7882A399225F6DA6F8B476D0C92812053B05194DEE82DCA228EECB3105BA2B815FA8B073306AE8CF1B8C44F72AF4A8D78C2DD771EEE543733C87C5FD8F1FE016B5F245174C6D9F01664590A45C738B18B8CBD8E754992AA262D404C24BD71F2008BE1E9F9FD589F7B18354B9870A2751FE4E7B093CD5B0990AF60077B9C7D9BB44511CACB10C03F538071AF9F9721698EF',

exponent: '0x10001',

valid_from: 'Aug 24 00:00:00 2016 GMT',

valid_to: 'Aug 24 23:59:59 2018 GMT',

fingerprint: 'FD:8F:F8:A4:F9:8C:11:C0:3E:19:35:22:F9:F0:ED:45:E3:C6:8A:8E',

ext_key_usage: [ '1.3.6.1.5.5.7.3.1', '1.3.6.1.5.5.7.3.2' ],

serialNumber: '6CFCED79A1F0CF5B82B7FA7D32114000',

raw: <Buffer 30 82 06 84 30 82 05 6c a0 03 02 01 02 02 10 6c fc ed 79 a1 f0 cf 5b 82 b7 fa 7d 32 11 40 00 30 0d 06 09 2a 86 48 86 f7 0d 01 01 0b 05 00 30 7e 31 0b ... > } }

Thanks

Solved Solved
0 3 235
1 ACCEPTED SOLUTION

Hey James,

Looks like there may be a self signed TLS cert in that chain somewhere. You can try setting the following environment variable as a work around

export NODE_TLS_REJECT_UNAUTHORIZED=0

That could possibly resolve the TLS issue you're seeing with EM.

-Matt

View solution in original post

3 REPLIES 3

Hey James,

Looks like there may be a self signed TLS cert in that chain somewhere. You can try setting the following environment variable as a work around

export NODE_TLS_REJECT_UNAUTHORIZED=0

That could possibly resolve the TLS issue you're seeing with EM.

-Matt

Not applicable

Hi Matt, thanks! This looks like a SSL certificate issue. I changed the virtual hosts configuration to make microgateway to point to a http gateway instead of https and this issue is gone

Great news. Glad you found a work around.