onvif
Storage Configuration - Renewal of cloud storage credentials
With the current specification, a cloud provider must continuously renew the credentials assigned to a device using the SetStorageConfiguration API. This means that a cloud provider must keep track of all devices and attempt to refresh this configuration, generally over Uplink, regularly to ensure that there is no loss of recording.
Instead of a manual procedure by the cloud provider, we propose that the device manage the lifecycle of its credentials on its own, by accepting an endpoint to a simple API that provides credentials to the device on-demand. This will allow the device to refresh credentials much faster in case of outages, where the device comes back online after a while and wants to resume recording as quickly as possible.
To be Added: An OpenAPI document defining the schema of the response that device should expect from the API
Updated based on feedback from F2F:
- Removed the content-type completely. So application/json is just assumed, but has no impact.
- Removed LocalPath & Type fields from the renewal response. It doesn't make sense to change those during a renewal.
- Clarified that null values are expected to clear the corresponding optional parameter
- Clarified that the storage configuration shall be updated with the values from the renewal. So that further GetStorageConfigurations will see the current values.
@jmelancongen Once PR https://github.com/onvif/specs/pull/481 is approved, you may want to update the CertPathValidationPolicyID used to validate the renewal endpoint server certificate. requirement to reflect proposed changes in https://github.com/onvif/specs/pull/481 ?
