Thanks Aleksey. As per spec, "sct" of doxm captures the list of Credential types supported by the Device. But, Looks like during ownership transfer, we will always install "PSK" as default Owner Credential(OC), instead of checking of the supported credential types of the device. What if the device is not supportING "PSK".
Is it possible to do Ownership re-transfer?? Let's say, using Mobile(as OBT), a new device is onboarded and owned. After a while, if the user changes to a new Mobile, how can the ownership of the device be transferred from the old Mobile to new Mobile. -Ravee On Wed, Feb 28, 2018 at 7:15 PM, Oleksiy Volkov <a.vol...@samsung.com> wrote: > Hi Ravee, > > > > By default, Client #2 can only discover resources after otm, but doesn't > have access to them. > > But Client #1 can provision additional credential and acl > records regarding Client #2 to device, and Client #2 will have access to > certain resources on this device after onboarding. > > This method should work, but I've never tested it before... > > > > *Best regards,* > > *Aleksey Volkov* > > > > --------- *Original Message* --------- > > *Sender* : Raveendranath Kondrakunta <raveendranath.kondraku...@gmail.com> > > *Date* : 2018-02-27 16:37 (GMT+2) > > *Title* : [dev] Ownership Transfer > Hi, > > During the onboarding process, the Device ownership is established using > an Onboarding Tool(say a Mobile App). Once, the new device is onboarded, > the new Device /oic/sec/doxm devowneruuid is set to the uuid of the > Client#1(on Mobile#1). > > Assuming, default Credential and ACL Provisioning by the stack. Can a > different Client#2(on Mobile #2) discover and access the resources of this > new Device? > > How can a particular Mobile app, running on different phones, have equal > access and ownership to the resources of the new Device? > > I'm planning to use Just Works as OTM and no Cloud support in the Mobile > App. > > -Ravee > > _______________________________________________ > iotivity-dev mailing > listiotivity-dev@lists.iotivity.orghttps://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > > > > > > > > > >
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
