Storage Configuration - Renewal of cloud storage credentials #423
Conversation
|
To be Added: An OpenAPI document defining the schema of the response that device should expect from the API |
jmelancongen
changed the title
|
Updated based on feedback from F2F:
|
|
@jmelancongen Once PR #481 is approved, you may want to update the CertPathValidationPolicyID used to validate the renewal endpoint server certificate. requirement to reflect proposed changes in #481 ? |
| meantime to avoid service disruption. | ||
| </para> | ||
| <para> | ||
| Once the device has called the renewal endpoint, the corresponding <literal>StorageConfiguration</literal> shall be updated with the |
There was a problem hiding this comment.
Is it really necessary to update the static configuration on flash? Besides the unwanted side affect of writing to flash unnecessarily often it does not seem logical to change the static configuration with the dynamic fetching of tokens.
There was a problem hiding this comment.
Since the alternative was pushing an update to the configuration anyway it doesn't feel too different. Of course the requirement does not mandate the device writes it to persistent storage, as long as it gives the right response on GetStorageConfiguration the device may remember it anywhere it wants I feel.
The main reason I see this as needed is to facilitate troubleshooting in case something goes wrong. The client can query the device state to figure out what is currently in use and attempt to resolve the situation
Co-authored-by: Kieran McCartan <[email protected]>
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.