Unable to invoke Conduit API, with firmware version 5.1.6

[Ajay K]

we upgraded to the new gateway and here is what I have from the home page on the gateway for the model and version of firmware.

mPower™ Edge Intelligence Conduit – Application Enablement Platform
MTCDT-L4N1-246A Firmware 5.1.6

In the older gateways and the firmware versions of 1.7.4 I could connect to the gateway/conduit API without any issues, for example if I wanted to login I would just run the following URL.
“https://192.168.2.1/api/login?username=admin&password=somepwd” and I would successfully login and I would get a token which I can continue to use in calling other API’s without any issues. However in the new Gateway/Conduit and firmware version 5.1.6, I can’t even login using the above URL, the conduit immediately closes the connection, as soon as the request is made. Any idea how I can over come this issue?

System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

Thanks,
Ajay

[Ajay K]

Any thoughts, its breaking a lot of our automation we have built setting up the conduit.

[Jason Reiss]

I was able to get a login token if I passed the data in the body rather than the query string. Does this help?

curl -k https://172.16.33.152/api/login --data '{"username":"admin","password":"somepwd"}'

[Jeff Hatch]

Hello Ajay,

Here is another curl version I have used in a bash script in the past.

curl -s -k -X POST “${ADDRESS}/api/login” -d “username=${LOGIN}” -d “password=${PASSWORD}”

The curl utility usually defaults to a GET unless so this one explicitly does a POST. Also, the -d options are the same as Jason’s, just there are two data parts. I’m not sure that specifying the creds on the URL is supported anymore.

Jeff

[Ajay K]

Hi Jason/Jeff,

Sorry for the false alarm, since the Https settings by default in the new conduit is configured to TLS 1.2, I had to ensure that the security protocol being used to communicate over https is TLS 1.2 and it works both using the Curl and using a .NET Http client as well.

Thanks,
Ajay

[Ajay K]

Just curious what was the https security protocol used in 1.7.4 version? Was it TLS 1.1 or SSL3?

Thanks,
Ajay

[Author]

Posts