Per-account device registration + key-value store

[felix-schwarz]

Is your feature request related to a problem? Please describe.

During discussion of https://github.com/owncloud/ocis/issues/2793, it showed that it would be beneficial if it was possible to control which devices sync which set of content.

This could be controlled by device classes (mobile, computer) or device types (phone, tablet, laptop, desktop) or, more granular, on a per-device basis.

There are probably more contexts within which a list of devices will be useful.

Describe the solution you'd like

Authenticated clients should be able to:

1) register a device in an account, with the following information:

• a device UUID (generated on the device itself) that persistents across sessions
• a shared secret UUID (generated on the device itself) that's only transmitted during registration, for future-proofing (in case a client needs to proof its authenticity in the future)
• device name (John Doe's iPhone)
• device class (mobile, computer)
• device type (phone, tablet, laptop, desktop)
• platform (android, desktop, ios)

2) retrieve a list of devices, with UUID + name

3) retrieve and modify (set + delete) a per-account, per-device key/value store. Any JSON value should be supported as value. Readonly keys should be possible, i.e. if the server computes a key's value dynamically (depending on other values and server configuration).

This would enable interesting use cases:

• users could choose which spaces to sync, on a per-device basis, in one spot
• admins could choose which spaces to sync, on a device-class basis (assuming: the server uses the registration info + the client determines whether it should sync a space based on a server-computed property, such as f.ex. a specific tag)
• admins could allow access to a space or folder on a per-device basis (first use case for the shared secret UUID!)
• remote wipe: tell a specific device to erase its local copies or more (another use case for the shared secret UUID)
• forensic / logging: identify device from which an access occurred

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.