| Re: [hono-dev] Redundant(?) properties in API messages |
|
Hi Kai,
I'm digging into the last bits of Hono and I see you have already implemented the "one sender for tenant" sematic in order to connect to the dispatcher. I still see a problem on authorization side with the current TelemetryClient example because the hasPermission() method searches for the deviceId inside the address that from the sender client is /telemetry/myTenant (the device id is still in the "to" property). Is it just because the TelemetryClient isn't aligned in terms of source code ? Thanks, Paolo. Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor > To: hono-dev@xxxxxxxxxxx > From: gsim@xxxxxxxxxx > Date: Wed, 27 Apr 2016 15:26:56 +0100 > Subject: Re: [hono-dev] Redundant(?) properties in API messages > > On 27/04/16 14:14, Hudalla Kai (INST/ESY1) wrote: > > We will now try to use a sender (with target address) per tenant when forwarding the telemetry messages to the dispatch router. > > > > However, since I think that being able to authorize at the device level (when receiving telemetry data) as well, it would be great if the dispatch router would at some time support what you promised :-) > > > > Any chance for that? > > Yes, I think there will be more flexible routing at some point. > _______________________________________________ > hono-dev mailing list > hono-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/hono-dev |