@kwlodarczyk Yes it is mandatory: https://openconnectivity.org/draftspecs/Gaborone-1/OCF%20Cloud%20API%20for%20Cloud%20Services.pdf section 8.2 .
@ondrejtomcik @jkralik Is there a way for a client to find out what events has be already subscribed to? Suppose I want to subscribe to an event but I'm not sure if I already subscribed or not. I just checked that I'm able to subscribe to same event with same eventsUri multiple times and the Go-OCF cloud allows me to do that.
@jkralik the problem is that not always you are able to unsubscribe before the app losts track of the subscriptionID. In my case I was not able to run the test cases I'm developing against Go-OCF Cloud right now because instead od receiving one event I get a whole bunch of them which causes verifications to fail.
@Hugh-Bao There are no specific guidelines, only specification which is fully implemented. Yes, you can use one "eventURL" for all subscriptions.
Yes, you can with postman test the C2C in a way that pluggedin.cloud is a target cloud. But you want be able to receive events with postman. For that you need another tool. e.g. https://ptsv2.com/
@kmaloor @ondrejtomcik Hi, I'm experiencing issues with running more than one cloud server device (cloud_server lite app, run from separate copies of Lite repos). One device works fine, i.e. it is visible as online in Go-OCF portal, however the second device cannot log in to the cloud and is visible as offline. I tried that multiple times and I'm always getting the same result. Am I doing something wrong?
@kwlodarczyk subscription retrieval API will be released in next spec release cycle. Another way how you can clean it up - reply 4xx to received event. Particular subscription should be then canceled. Do we have this implemented @jkralik ?
@kwlodarczyk @ondrejtomcik You need to return http code 410 (StatusGone ) to remove subscription.
A simple question of the client parameters (client id and client secret) under OCF C2C API context, are these parameters assigned to the "vendor client APP" (just use this term to mean the registered client is associated with the vendor of the Orgin Cloud) of the Origin Cloud, or the "end user" signing in the origin cloud with the the "vendor client APP" for account linking? I assume it is the former. Am I right? I also assume the Target Cloud should assign the same client parameters for the same "vendor client APP", there could be different end-users linking their accounts, but should associate with the same client parameters.
Hello @johnzhangjun . Client parameters are created per vendor. Each vendor accessing e.g. plugged.in C2C API will have their own, unique client credentials, redirect uri, etc. Then the vendor will provide account linking, for which he will use these values and user will be informed on the plugged.in side that hey, this app (client) wants to r/w your devices.
@ondrejtomcik Hello Ondrej, there is one problem that I can not hande it. Can you give me some advices. When I deploy go-ocf cloud in my local Ubuntu 18.04 enviroment, if I could use curl or postman to constuct C2C APIs for accessing the content from cloud mentioned as above, how can I configure relative ENV by using docker ?
Hello @ondrejtomcik I can get access token from local ocfcloud/bundle:vnext when I issue "curl 'https://localhost:9085/api/authz/token' -k" request ; but I will receive "404 not found" response while I send "curl --request GET \
--url https://localhost:9085/api/v1/devices \
--header 'authorization: Bearer <access_token>' \
--header 'content-type: application/json' \
--header 'accept: application/json'", what causes this problem. Looking forward to your replying, thank you!
--url https://localhost:9085/api/v1/devices \
--header 'authorization: Bearer <access_token>' \
--header 'content-type: application/json' \
--header 'accept: application/json'", what causes this problem. Looking forward to your replying, thank you!
@Hugh-Bao You mean full cloud, not the bundle? deployment scripts and docu is not finalized yet. There is unfortunatelly no guidance how to do it. Our resources are very limited and everything takes time. Until you want to sponsor the go-ocf project and speed up your request. In the upcoming days, there will be an official sponsorsip possiblity enabled for the go-ocf/cloud project, which might speed-up your request.
