search

onvif / specs

ONVIF Network Interface Specifications
Other
345 stars 93 forks source link

Cloud integration specification #428

Closed ocampana-videotec closed 2 months ago

ocampana-videotec commented 5 months ago

Creating the draft pull request to gather feedback

jflevesque-genetec commented 4 months ago

Missing share token definition in the XML so that the Cloud VMS can know which endpoint to contact on the Manufacturer Cloud

jmelancongen commented 3 months ago

I would like to see the Onboarding segments landing before adding more stuff to that PR. Can we split the FW stuff into a distinct PR so we can prototype and merge the Onboarding stuff on its own since it already had large agreement. Then we can work toward what we want for everything FW related?

ocampana-videotec commented 3 months ago

Missing share token definition in the XML so that the Cloud VMS can know which endpoint to contact on the Manufacturer Cloud

I do not understand the problem. Can you please explain a bit more?

jflevesque-genetec commented 3 months ago

Missing share token definition in the XML so that the Cloud VMS can know which endpoint to contact on the Manufacturer Cloud

I do not understand the problem. Can you please explain a bit more?

In the past presentations, we discussed that the share token would be obtained from the manufacturer cloud in an undefined way. That share token is then given to the operational cloud. To be able to start the transfer operation, the share token needs to have information related to the manufacturer's cloud endpoint. Since this should be part of the share token, it needs to be defined as part of the share token model in the specification.

ocampana-videotec commented 3 months ago

Missing share token definition in the XML so that the Cloud VMS can know which endpoint to contact on the Manufacturer Cloud

I do not understand the problem. Can you please explain a bit more?

In the past presentations, we discussed that the share token would be obtained from the manufacturer cloud in an undefined way. That share token is then given to the operational cloud. To be able to start the transfer operation, the share token needs to have information related to the manufacturer's cloud endpoint. Since this should be part of the share token, it needs to be defined as part of the share token model in the specification.

Didn't we agree to leave the token format vendor specific? eventually, the only thing that we need from an OCS is that it should univocally identify one single device within the MCS.

jmelancongen commented 3 months ago

We said it had to have at least a bit of a standard shape, like JWT with at least one mandatory claim: The URL of the manufacturer endpoint. Otherwise how is a client to know Who it should call for a given transfer token? We didn't want to have a central repository or anything of the sort, so the option we had remaining was that the transfer token needed to be self sufficient and give that information to the client

Just for reference, we found that shape mentioned here: https://wush.net/trac/onvif/browser/wg_enh/2023/Proposals/cloud_onboarding/20240118_CloudOnboarding.pptx Slide 3