Adapt to the OCM spec for remote shares
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
feature: federation
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
[!TIP]
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
There's been work at cs3org towards standardizing federated shares, adopting a draft for an OCM spec [1].
To adapt nextcloud to this standard, we would need to:
- Allow Bearer auth for incoming and outgoing remote shares
- Use permanent refresh tokens and transient access tokens for the shares
- Update the nextcloud OCM stuff to include the token endpoint
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked OCM specification and locating Nextcloud's existing OCM implementation for remote shares. Compare the current authentication and token handling with the draft requirements for Bearer authentication, permanent refresh tokens, transient access tokens, and the token endpoint. Done means incoming and outgoing shares conform to the agreed OCM behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100