Node.JS Error: Hostname/IP doesn't match certificate's altnames

Not applicable

Since moving to our own certs in a keystore and a vhost I have a problem with an error message when I call a API Proxy from within a Node.JS application.

The issue only occurs when the Node.JS is run from EDGE and prior to migrating to our own CName and when using org-env.apigee.net this worked fine. When running locally the issue does not occur.

I can call the API Proxy in question without any problem from another Proxy on EDGE using a Service Callout and the problem only occurs when called from EDGE via Node.JS. The annoying thing is I cannot, of course, call the Proxy from the Node.JS directly and need to call it externally due to the limitations in Apigee.

The Node.JS that I am using to call the API Proxy is using the Request Module and the relevant code is below:

Any help gratefully recieved.

jsonObj = {};
jsonObj.resources = [path];
jsonObj.subject = {"ssoToken": session_token};
jsonObj.application = "API Policy";


var headers = {
	'Content-Type': 'application/json',
	'iplanetDirectoryPro': session_token
};


var options = {
	url: 'https://example.com/forgerock-connector/json/policies?_action=evaluate',
	method: 'POST',
	headers: headers,
	body: jsonObj,
	json: true
};


request(options, function (err, res, body) {
		
if (err) {
	result.code = 500;
	result.message = "getrights: " + err;
	callback (result);
} else {
	result.code = 200;
	result.message = JSON.parse(body);
	callback (result);
}
0 1 3,601
1 REPLY 1

Hey Philip

I'm not sure this is the right subsection for the question. You may want to move this question to the edge part of the community.

-Matt