We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

OC heart File-Service

1
 Cite
 Share
 Related Material
 Download
 Purchase
No logo availableownClouders
 Roth, Michael Boogaart, Gregor van den

Formal Metadata

Title
OC heart File-Service
Title of Series
Number of Parts
22
Author
Contributors
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
We are trying to open our central, scalable, multi-protocol (SMB, NFSv4) NAS/File-Service, to Sync usage. Challenges to tackle: 1. Impersonation: OC accesses the users data, "as" the user. It therefore obtains a Kerberos ticket and accesses as NFSv4-Client. This enables Sync usage, but ... 2. ... in order to pick up changes, scanning has to work reliable and quick, see e.g. bug [#11797](https://github.com/owncloud/core/issues/11797). 3. CRUDS vs. ACLs: To enable sharing of File-Service data, ACLs have to be automatically set, modeling OCs CRUDS permissions. 4. Transparency: The further goal is to enable all usage patterns (access, sync, share, configure share, ...) over all protocols.