Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

ocfcloud/Lobby

https://plgd.dev/

People

Repo info

Activity

Ondrej Tomcik

@ondrejtomcik

ok. that’s good. Looks like misconfiguration. What about device logs ?

could you please send me response from
https://{yourip}:8443/.well-known/ocfcloud-configuration

Wouter van der Beek

@WAvdBeek

Ondrej Tomcik

@ondrejtomcik

:) Looks good. Device is owned and coapcloudconf was successfuly set.
Are you starting bundle also with -p 5684:5684

Wouter van der Beek

@WAvdBeek

{"access_token_url":"https://192.168.178.85:8443/oauth/token?client_id=test\u0026audience=test","auth_code_url":"https://192.168.178.85:8443/authorize?client_id=test","cloud_authorization_provider":"test","cloud_certificate_authorities":"-----BEGIN CERTIFICATE-----\nMIIBZDCCAQqgAwIBAgIQLWopKNaGWt+5PHVrKMxf7jAKBggqhkjOPQQDAjASMRAw\nDgYDVQQDEwdSb290IENBMB4XDTIxMDMwNDEzMzQzMVoXDTIyMDMwNDEzMzQzMVow\nEjEQMA4GA1UEAxMHUm9vdCBDQTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABBhM\nkv+/ZEjAKIrAf3bPI46dwZ0k1+EGP3Fq20ZQ+gEBxmpOamMtoxufy0LS+3xUn0K1\nECdzeUdCxa609khnbuyjQjBAMA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTAD\nAQH/MB0GA1UdDgQWBBS2WXnDa2r14Heibt9QmvQWrE6DyzAKBggqhkjOPQQDAgNI\nADBFAiAZ61wtgIqcloso1u9fABh0kISIcmBdUqnYcAfeoQ3NYAIhAIRTTAy/8KSc\nla3KkdMmJ+XwcjvroK87+DcfNHeciM1p\n-----END CERTIFICATE-----\n","cloud_id":"00000000-0000-0000-0000-000000000001","cloud_url":"coaps+tcp://192.168.178.85:5684","jwt_claim_owner_id":"sub","signing_server_address":"192.168.178.85:8443"}

-p 5684:5684 is there

Ondrej Tomcik

@ondrejtomcik

ah I can see the problem

Wouter van der Beek

@WAvdBeek

but that port is not listed in the output...

Ondrej Tomcik

@ondrejtomcik

@jkralik bundle has wrong configuration of cloud_authorization_provider

Wouter van der Beek

@WAvdBeek

e is 65537 (0x010001)
starting nats-server
starting mongod
Try to reconnect to mongodb(localhost:10000) 1
starting oauth-server
Try to reconnect to oauth-server(localhost:9088) 1
starting authorization
Try to reconnect to authorization service(localhost:9085) 1
starting resource-aggregate
Try to reconnect to resource-aggregate(localhost:9083) 1
starting resource-directory
Try to reconnect to resource-directory(localhost:9082) 1
starting coap-gateway-unsecure
starting coap-gateway-secure
starting grpc-gateway
Try to reconnect to grpc-gateway(localhost:9084) 1
starting http-gateway
Try to reconnect to http-gateway(localhost:9086) 1
starting certificate-authority
Try to reconnect to certificate-authority(localhost:9087) 1
starting nginx
Open browser at https://192.168.178.85:8443

but only the reconnects are logged.. so it might be ok

Ondrej Tomcik

@ondrejtomcik

@jkralik can he changed it using env variable from test to plgd?

Wouter van der Beek

@WAvdBeek

ok, i just pressed the big red thing which is a device reset button.

something happend on the device: cloud manager status: Failed

but it also says that it installed successfully the PKI certificate chain.

Ondrej Tomcik

@ondrejtomcik

yes. problem is on our end. Already created MR

Build takes pretty long, I will give you new plgd cloud image in 40 mins.

plgd-dev/cloud#206

Wouter van der Beek

@WAvdBeek

ok, let me know when i can download it with docker

Ondrej Tomcik

@ondrejtomcik

I will give you a new tag.

Wouter van der Beek

@WAvdBeek

pretty cool by the way...:)

Ondrej Tomcik

@ondrejtomcik

your satisfaction can be reflected in opencollective :-D
https://github.com/plgd-dev/cloud
https://opencollective.com/plgd-cloud

Ondrej Tomcik

@ondrejtomcik

OR even better, contribute with documentation - how to start with secure and unsecure device together with bundle and plgd mobile app! That would be awesome!

https://github.com/plgd-dev/cloud/tree/v2/docs/guide/getting-started
@WAvdBeek :-)

Ondrej Tomcik

@ondrejtomcik

@WAvdBeek plgd/bundle:v2next-d55f695

let me know if it works
you need to reinit your mob app

Wouter van der Beek

@WAvdBeek

i am still debugging the update.. it looks like that plgd is checking the input and somehow this is failing the input check?

Ondrej Tomcik

@ondrejtomcik

Hm. Could you please go to developer console of your browser and check full response for that update request? If there are more information about the error.

Wouter van der Beek

@WAvdBeek

ed to load resource: the server responded with a status of 503 ()
utils.js:65 Uncaught (in promise) TypeError: t is not a function
at ft (utils.js:65)
at things-details-page.js:107
at u (runtime.js:63)
at Generator._invoke (runtime.js:293)
at Generator.throw (runtime.js:118)
at r (asyncToGenerator.js:3)
at l (asyncToGenerator.js:29)

the 503 is intentional..

not sure yet if this is a plgd problem. trying to debug with devicespy and i also see things that are weird.

Wouter van der Beek

@WAvdBeek

ok, this was not a plgd issue... issue is solved, e.g. update is working nicely from plgd to the device.

i am OoO tomorrow, so i will try the security solution next week.

Ondrej Tomcik

@ondrejtomcik

@WAvdBeek I was able to replicate your issue with update as well - such an error is returned when such a property is not editable - or simply when IoTivity-Lite rejests the request.
Enjoy your time off and hear you on Monday.

Kyle Haefner

@khaefner

@ondrejtomcik regarding documentation, Clarke and I are working on an article for embedded, which will be pretty much a user guide on how to do all of this, it should not be a huge lift to update the documentation.

Soneca-ii

@Soneca-ii

Hi, a quick question. If creating an iotivity-lite server with CLOUD=1 ( secure and pki also) and placing the certificate from the PLGD I manage to onboard the device. Is there some workflow that I can do the same with an iotivity-lite server created with CLOUD=0 and configure it during the onboard?

Ondrej Tomcik

@ondrejtomcik

@Soneca-ii do you mean with plgd mobile app? CLOUD=0 has nothing to do with ownership transfer. It enables capability to onboard device to the cloud.

Wouter van der Beek

@WAvdBeek

Hi Ondrej, the onboarding securely to the cloud now works.. I tried it out with a fresh instance of docker & device and it worked seamlessly!

i can now control the device securely from the cloud.

the app can't control the device?

Ondrej Tomcik

@ondrejtomcik

Hey @WAvdBeek
No, the application is just transfering the ownership to the authenticated user and setting the coapcloudconf resource. The API of the plgd.mobile supports it, but UI would have to be developed. To have at least easy onboarding we did this simple one button plgd app :)

Wouter van der Beek

@WAvdBeek

Ok thanks, I hoped I missed something. I agree that the app is simple and works correctly and simple for onboarding.

the issue that i have now is that I have to onboard devices that are talking to the cloud proxy, hence I need an OBT that does cloud setup and onboarding.. reading the email of Kishen that does not yet exist. So i will add that code in the iotivity OBT (commandline).

to make this work I need to have the data to onboard the plgd cloud, e.g. what is the security information (I only supplied the unsecure info as work around in the device that talks to the plgd cloud)

Ondrej Tomcik

@ondrejtomcik

@WAvdBeek could you please describe the flow, what needs to be done to onboard devices that are talking to the cloud proxy? How are these devices discovered? Are they onboarded separately or is it enough to onboard cloud proxy itself?

I didn’t track this topic in the OCF, so feel free to point me to some sequence diagram in the KAVI.

Wouter van der Beek

@WAvdBeek

It is CR2599

the cloud proxy (my own code, not yet released) can be onboarded to plgd with plgd app.

the issue is then that the client of the cloud proxy that talks to the OCF devices needs to be configured, hence the plgd app is not doing that.

Chat via Matrix