Missing or invalid parameter(s). No delivery channel found based on key 'https'. | Thales IoT Developer Community
March 23, 2016 - 1:29pm, 5447 views
Hi,
What is the cause behind this message when I'm trying to create a HTTPS Notification?
https://partner.api.sensorlogic.com/v5.0/notificationSubscription/create...
https://partner.api.sensorlogic.com/v5.0/notificationSubscription/create...
I was monitoring the given address and Sensorlogic server didn't even riched out for this address. The address by default returns 404 but it can not be the cause now. I tried many other addresses too.
I followed the documentation sample and I can not see anything wrong with the URL.
https://api.sensorlogic.com/v5.0/notificationSubscription/create.json?to...
I got this response:
{
"apiVersion": "5.0",
"header": {
"status": "ERROR",
"messages": [
{
"code": "102",
"string": "Missing or invalid parameter(s). No delivery channel found based on key 'https'."
}
]
},
"body": {}
}
What's missing or which check is failing?
Hello,
Your requests seems correct. You are using %20 while in the example there is + but this should not be the case.
If you get this error response from server to your requests the notifications will not be sent to the specified address.
Have you tried with other channels like email or sms? Is there also error response?
I'll try to consult this problem and get more information.
Regards,
Bartłomiej
Hi,
Thank you. I tried to execute the same unit test to make the subscription with email but I have other problem now. I get "HTTP/1.1 403 Forbidden" response to my first guess was the time is not in sync so I wanted to double check but I got response:
--- (request) --->
GET https://partner.api.sensorlogic.com/v5.0/tools/time?authUser=***&authOrg...
<--- (response) ---
HTTP/1.1 403 Forbidden
Content-Length: 217
Content-Type: text/html; charset=iso-8859-1
Date: Wed, 23 Mar 2016 18:23:47 GMT
Server: WAF
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access /v5.0/tools/time
on this server.</p>
</body></html>
I tried to open the link is different browser and I got invalid certificate response. The server use wildchar certificate for CN=*.sensorlogic.com and it works fine with "api.sensorlogic.com" but not its subdomain so partner.api.sensorlogic.com cause common name invalid exception and browsers (and some other clients) may not advise to access to the server.
Is there any security limit that may block my request or any other reason why suddenly my unit tests start failing when I didn't change the credentials? Once I can access again I will try the email or sms. So far the documentation and the service don't seem to be reliable so I have hard time to achive a simple result. Create a demo app to present the device management and notifications.
Thank you any help in advance.
Regards,
Laszlo
Hello,
The error from your previous post is not connected with authentication failure so your time must have been correct.
It is written in the document that the signature generation test API is not available on production environments so this is probably the reason of "HTTP/1.1 403 Forbidden" reply. Or have you been able to use this test API before on this server?
Regards,
Bartłomiej
Hi,
I'm testing only the https://partner.api.sensorlogic.com endpoint now. I don't know why but the server suddenly started to respond with "403 Forbidden" to any request. I didn't change any credential information and I didn't reach the API call limit and I didn't change the test script either. I don't understand why suddently my test script failing with "403 Forbidden" response from server. Everything worked before (except I was not able to make the https subscripttion) but now I'm blocked and I can not work on the original issue. Could you pleasse check the "FORGEROCK" organization if there is any issue with that. From the Admin UI I can not see any issue.
Hi,
Some progress, I changed from HTTPS to HTTP http://partner.api.sensorlogic.com/v5.0 and it works again. So I tested with email and it successfully made the subscription but https is still failing.
More progress, I chagne the paramer from https to deliveryChannel=http and it works. The documentation is incorrect.
Hello,
I finally got the information about http/https support: HTTPS is not supported on Partner (Demo / trial) platform but only on the production server.
Regards,
Bartłomiej