Re: [m2m-iwg] Authentication in CoAP

[Julien Vermillard <jvermillard@xxxxxxxxx>]

basically yes, key based.
--
Julien Vermillard :::: http://people.apache.org/~jvermillard/


On Wed, Jan 29, 2014 at 4:59 PM, Tim Kellogg <tim@xxxxxxxxxxxx> wrote:
> Hi Julien,
>
> Could you elaborate on how to use DTLS for authentication? Is this similar
> to how Github uses public keys to identify & authenticate when pushing?
>
> Tim Kellogg
> Sr. Software Engineer, Protocols
> 2lemetry
> 605-593-7099
> @kellogh
>
> On January 29, 2014 at 8:56:41 AM, Julien Vermillard (jvermillard@xxxxxxxxx)
> wrote:
>
> Hi,
> I'm not sure it's the good mailing list for this kind of question, but
> I'm not sure which one is the good one :)
>
> CoAP doesn't support auth in the way HTTP.
> I think if you want to add security (authentication) on top of CoAP
> the usual way is to use DTLS (which is supported by Californium).
>
> The LWM2M ACL model is really specific to the problem it's solving:
> device management with multiple servers, I don't think it's what you
> are looking for.
>
> HTH
> Julien
>
> --
> Julien Vermillard :::: http://people.apache.org/~jvermillard/
>
> On Wed, Jan 29, 2014 at 4:18 PM, Tim Kellogg <tim@xxxxxxxxxxxx> wrote:
>> Hi,
>>
>> I'm working with Californium and I'm stuck on authenticating the sender.
>> Is
>> there some sort of analogous construct to HTTP's Authorization header?
>>
>> I've heard that lwm2m has an ACL object that might be used for this, but
>> does lwm2m integrate with Californium?
>>
>> Thanks,
>> Tim
>>
>>
>> _______________________________________________
>> m2m-iwg mailing list
>> m2m-iwg@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2m-iwg
>>
> _______________________________________________
> m2m-iwg mailing list
> m2m-iwg@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2m-iwg
>
>
> _______________________________________________
> m2m-iwg mailing list
> m2m-iwg@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2m-iwg
>