2.0.3 http request node with tls - valid certificates no longer work

General
1

I upgraded my instance today to 2.0.3 from 1.3.5 and noticed all of my HTTP request nodes are displaying errors under the node "SELF_SIGNED_CERT_IN_CHAIN" However the server these are going to has a valid cert, and openssl verify against the CA cert, comes back successful. I restored my backup from 1.3.5 install and everything works fine. The only way I have identified to get rid of the errors is to turn off certificate verification, but even with a valid cert, valid ca present nodered request node seems to think its untrusted or self signed.

Anyone else exhibit this?
example flow (works in 1.3.5, fails once upgraded to 2.0.3):

[
    {
        "id": "ede8f8bc3ed1d623",
        "type": "http request",
        "z": "90a227ad3d39d234",
        "name": "",
        "method": "POST",
        "ret": "txt",
        "paytoqs": "ignore",
        "url": "https://em01.ag.home.lab/api/login",
        "tls": "06b9d026eb93bb05",
        "persist": false,
        "proxy": "",
        "authType": "",
        "credentials": {},
        "x": 400,
        "y": 400,
        "wires": [
            [
                "7ff06071f1d48158"
            ]
        ]
    },
    {
        "id": "06b9d026eb93bb05",
        "type": "tls-config",
        "name": "CA Verify",
        "cert": "",
        "key": "",
        "ca": "",
        "certname": "",
        "keyname": "",
        "caname": "ca01",
        "servername": "",
        "verifyservercert": true,
        "alpnprotocol": "",
        "credentials": {}
    }
]

error returned in debug message:

RequestError: self signed certificate in certificate chain

Anyone else run into this? I checked github issue tracker and didn't see any relevant issues opened so figure I'd check here first.

2

Please do raise an issue.

3

Ok, will move this discussion to issue tracker. Thanks for the quick reply!

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.