Skip to Content

401 Authentication error in a REST POST(IOT 4.0 on Cloud Foundry)

Nov 28, 2017 at 11:19 AM


avatar image
Former Member

Hi All,

We had a working scenario in the NEO platform where the IoT services accepted data from the device based on the OAuth token of the device.

Data was posted to https.//..../<Device ID> successfully.

Now to implement the same on Cloud Foundry(IoT 4.0), we have a problem.

The configured IoT device doesnt generate an OAuth like in NEO, but a PEM certificate and a private key which our physical device cannot use.

Our physical devices are incapable of 2 way authentication using certificates.

Posting data on https://..../iot/gateway/rest/measures/<Device ID> fails.

Any idea how to get OAuth authentication working on the new IoT(4.0) platform?



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Anton Levin
Nov 28, 2017 at 12:49 PM

Hello Vivek,

security flow between IoT components on Neo [1] and CF [2] is different (see figures). Direct message sending from devices to the Gateway Cloud (on CF) supports certificate based authentication only as you have noticed.

However, you may want to leverage Gateway Edge (REST) [3] which will send messages to the Message Management Service on behalf of devices and do the necessary certificate authentication.






Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Anton,

Thanks for the response, I will explore option 3.