daniel.moran

The IoT Agent authenticates against the Context Broker just when there is a Trust token associated with the Device (you can do that with the `trust` provisioning attribute). You can...

Hello, sorry for the late response. The authentication features of the IoTAgent library are not commonly used (as the IoT Agents are usually deployed in the same network segment as...

Be aware that, for most of the components, the service path is not exactly hierarchical, as they only accept a single level in the hierarchy. The multitenancy mechanism is clearer...

There are currently several issues opened concerning how the service and servicepath flags work in the IoTAgents. I'm going to close all of them and leave this one as a...

Currently, all the attributes included in the OMA Registry are mapped, whether they have a DDF definition or not, but making some assumptions that may or may not be acceptable:...

The best way to avoid it is to explicitly declare those attributes in the device provisioning requests (using the internalattributes mapping). This is a really old issue, and we may...

And you are right. They shouldn't. It seems to me there may be some bug regarding active attribute registration. I'll try to check it.

I'm afraid none of the IoT Agents has been currently tested against the IoT Discovery GE. The GE used as a reference for the NGSI Protocol has always been the...

How are you testing that scenario exactly? I don't recall the server having a timeout for observations, but the server can, in fact, send an attribute to the client to...

Completely right; this is a bug in the implementation. We'll have to slightly change how the mapping works to overcome that issue.