nextcloud / nextcloud/documentation

Implement (or document) OCS API for Workflow Access Control List (ACL) feature

Open
#11,119 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop feature: workflows good first issue technical debt
Dominant language
JavaScript
Stars
628
Forks
2.5k
Avg merge
2d 11h
Merged PRs (30d)
135

Description

As it looks for me, there is no no way to access the Access Control List (ACL) feature for folder by remotecontrol.
I would expect it in OCS API. But i cannot find it.

Can you implement it?

This is my use case:
I program in a small team a software to generate template structures in nextcloud for similar workgroups on different locations. They have all the same workflow.
E.g. if a new work group starts, they shall have a predefined folder structure. Some people are admins, some have only read only status. ACL seems the right tool for us to allow to share files within groups as well as other groups. A manually configured setup works fine for us.
We made a webfrontent, to allow the management to create this structure by a simple button.

In Backgroup, Users are created and synchronized by LDAP feature. With OCS REST API it works great to make folders automatically. But we could not find a way to set the ACL rights automatically.

To impement it, we use KOTLIN as programming language. Our project is opensouce. It is named feather and feather frontend and is published in gitlab.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing OCS API documentation for remote control and the Workflow ACL feature. Determine whether the intended outcome is documenting an existing endpoint or designing and implementing new ACL access; the issue is complete only when one of those paths is specified and covered by usable documentation or an accepted API implementation.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.