[ACE-1717] Cloud Sync Take ownership of sync set action Created: 15-May-14  Updated: 21-Mar-17  Resolved: 21-Mar-17

Status: Closed
Project: Alfresco One Platform
Component/s: Synchronisation (Enterprise to Cloud)
Affects Version/s: None
Fix Version/s: None

Type: Feature Priority: Blocker
Reporter: Mark Rogers [X] (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 0
Labels: CloudSyncManager, Hybrid_Sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by MNT-13116 Content Added to Sync'd Folder in Clo... Closed
is related to by ACE-2254 Hybrid sync - missing use cases. Closed
is related to by MNT-11294 Possible http status ignored in “Remo... Closed
is related to by MNT-11545 Unclear error message when a hybrid c... Closed
Story Points: 13
Epic Link: Cloud Sync V2


When a user has left a company he may have files synced. to cloud How does hybrid sync cope with this ?

His credentials on cloud could be revoked so there's nothing hybrid sync can do to change anything on the cloud including removing the sync set.

In addition other users are not allowed to update the sync set.

Comment by Greg Melahn [X] (Inactive) [ 27-May-14 ]

Can this be fixed in the service-packs and merged forward.

Comment by Mark Rogers [X] (Inactive) [ 27-May-14 ]

I doubt that this can be done in a service pack. However Implementation is not yet designed or thought through.

One problem with this is that we want to tighten up the security around sync set ownership,

And that will make re-assign far more difficult.

One thought I have is that it would be possible for a user to "give up" their ownership. Which then allows another user to "take ownership."

However if the user is locked out then there needs to be some sort of admin "take ownership", And that's tricky because there's both client and server side permissions.

Comment by Gabriele Columbro [X] (Inactive) [ 29-Aug-14 ]

Did we make any decision on implementing this?

Comment by Mark Rogers [X] (Inactive) [ 29-Aug-14 ]


Comment by Mark Rogers [X] (Inactive) [ 20-Mar-15 ]

Part of answer for point 1 is that bad things happen and eventually sync stops working with no way to recover. It's a nasty problem.

We have this issue being worked on by ness at the moment. This issue is identified as the biggest problem stopping TS from syncing. For that issue I have proposed doing a minimal quick fix. But of course admin console and tools would be better.

Comment by Gabriele Columbro [X] (Inactive) [ 20-Mar-15 ]

Thanks Mark Rogers [X]. Can you link the issue here? Let's make sure we sync soon as I need to understand if/how we need to allocate more substantial sprint time to this.

Comment by Mark Rogers [X] (Inactive) [ 21-Mar-15 ]

MNT-13540 is in progress at the moment. I've sketched out a solution to take ownership of a sync set and give it to someone else. Requires a new rest api on cloud. Also function is only available to a cloud network admin. That's not ideal but I can't think of another simple option.

Comment by Derek Hulley [X] (Inactive) [ 21-Mar-17 ]

Cloud Sync features: we are not planning on making further enhancements. Should that change, this issue can be reopened or cloned to provide requirements.

Generated at Thu Jul 09 08:56:08 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.