| Re: [hono-dev] Hono-Kura integration |
|
ok makes sense,
this what I was expecting as well.
Thanks, Stefano
From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Hudalla Kai (INST/ECS4) <kai.hudalla@xxxxxxxxxxxx>
Sent: Tuesday, June 19, 2018 3:09:21 PM To: hono-dev@xxxxxxxxxxx Subject: Re: [hono-dev] Hono-Kura integration On Tue, 2018-06-19 at 13:01 +0000, Morson, Stefano wrote:
> Hi, > > just a quick question, > > do you seen any incorrect use of the /t/tenand-id/device-id/<topic-suffix> for > publishing of Kura messages in relation to the fact that /t/tenand-id/device- > id/<topic-suffix> has also the special semantic of an authenticated > gateway publishing data on behalf of a device ? > No, the difference between a device publishing data on behalf of itself and a gateway publishing on behalf of another device is just that the device uses credentials that resolve to the device itself whereas the gateway uses credentials that resolve to the gateway, i.e. not the device that it publishes data for. In the latter case the protocol adapters verify that the gateway is indeed authorized to act as a gateway for the device at hand. > Regards, > Stefano > From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of > Maiero, Matteo <matteo.maiero@xxxxxxxxxxxx> > Sent: Monday, June 18, 2018 10:49:48 AM > To: hono developer discussions > Subject: Re: [hono-dev] Hono-Kura integration > > Kai, Frank, > Thank you for the feedback. > I agree that, for our usage, the full topic is preferable and is the simplest > approach. > I believe we will go on with that. > > Best regards, > Matteo > > -- > Matteo Maiero > Senior Software Engineer > > direct: +39 0433 485 902 > email: matteo.maiero@xxxxxxxxxxxx > > EUROTECH > Imagine.Build.Succeed. > HEADQUARTERS > EUROTECH S.p.A. – Via Fratelli Solari, 3/a | 33020 Amaro UD | Italy | Tel. +39. > 0433 485411 | Fax +39. 0433 485499 | > Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine 196115 > www.eurotech.com > ____________________________________ > > Il presente messaggio ed ogni suo allegato sono da intendersi inviati > esclusivamente agli effettivi destinatari e potrebbero essere soggetti a > restrizioni legali. Se avete ricevuto questo messaggio per errore vi invitiamo > a darne immediata notifica al mittente e cancellarlo dal vostro sistema. > Qualsiasi altro uso di questo messaggio da parte vostra e' strettamente > proibito. > > This e-mail, and any file attached to it, is meant only for the intended > recipient of the transmission and may be a communication privileged by law. If > you have received it in error, please notify the sender immediately and delete > the original from your system. Any other use of this e-mail by you is strictly > forbidden. > > > On 13 Jun 2018, at 15:50, Hudalla Kai (INST/ECS4) <kai.hudalla@xxxxxxxxxxxx> > > wrote: > > > > On Wed, 2018-06-13 at 13:00 +0000, Maiero, Matteo wrote: > > > Hello, > > > Following yesterday’s discussion we continued the integration process in > > > Kura’s > > > enh_cloudPublishers branch [1]. > > > > > > From my understanding of yesterday’s discussion, there can be two topic > > > structures differentiated if the device is not authenticated (condition > > > only > > > usable for testing purposes) or authenticated. > > > For telemetry messages, for example, the supported non authenticated topic > > > is > > > in the following form: > > > > t/tenant/device/<topic-suffix> > > > So, for the DEFAULT_TENANT, device 4711 and topic suffix asset1, the > > > resulting > > > topic at which Kura can publish is: > > > > t/DEFAULT_TENANT/4711/asset1 > > > > > > For an authenticated device, the topic should be shortened, omitting the > > > tenant-id and device-id fields. > > > Referring to the example described above, the topic for an authenticated > > > device > > > would then be: > > > > t/asset1 > > > > > > Are my assumptions correct? > > > > > > > No, the topic "t/asset1" would be mistaken for a ResourceIdentifier whose > > endpoint component would be "t" (for telemetry) and whose tenant component > > would > > be assumed to be "asset1". That is because the second path segment (if > > existing) > > is always assumed to contain the tenant and the third segment (if existing) > > is > > assumed to contain the device ID. So, in your case you should simply publish > > to > > t/DEFAULT_TENANT/4711/asset1 in both cases. If the device is authenticated > > then > > the adapter will verify that the device ID and tenant ID that have been > > resolved > > as part of the authentication process actually match the second and third > > path > > segments. > > > > > Best regards, > > > Matteo > > > > > > [1] https://github.com/eclipse/kura/tree/enh_cloudPublishers > > > -- > > > Matteo Maiero > > > Senior Software Engineer > > > > > > direct: +39 0433 485 902 > > > email: matteo.maiero@xxxxxxxxxxxx > > > > > > EUROTECH > > > Imagine.Build.Succeed. > > > HEADQUARTERS > > > EUROTECH S.p.A. – Via Fratelli Solari, 3/a | 33020 Amaro UD | Italy | Tel. > > > +39. > > > 0433 485411 | Fax +39. 0433 485499 | > > > Cap. Soc. 8.878.946,00 € I.V. | P.IVA / C.F.: IT 01791330309 | REA Udine > > > 196115 > > > www.eurotech.com > > > ____________________________________ > > > > > > Il presente messaggio ed ogni suo allegato sono da intendersi inviati > > > esclusivamente agli effettivi destinatari e potrebbero essere soggetti a > > > restrizioni legali. Se avete ricevuto questo messaggio per errore vi > > > invitiamo > > > a darne immediata notifica al mittente e cancellarlo dal vostro sistema. > > > Qualsiasi altro uso di questo messaggio da parte vostra e' strettamente > > > proibito. > > > > > > This e-mail, and any file attached to it, is meant only for the intended > > > recipient of the transmission and may be a communication privileged by law. > > > If > > > you have received it in error, please notify the sender immediately and > > > delete > > > the original from your system. Any other use of this e-mail by you is > > > strictly > > > forbidden. > > > > > > _______________________________________________ > > > 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 > > _______________________________________________ > > 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 > > _______________________________________________ > 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 _______________________________________________ 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 |