Add "public" OCS endpoint to manage the avatar
Open
Nobody has claimed this yet.
1. to develop
client: 🤖🍏 mobile
enhancement
feature: profile
feature: users and groups
technical debt
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
So our beautiful clients can manage the avatar too.
Currently it's only possible via index.php/ which has CSRF protection that prevents mobile clients
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 tracing the existing avatar-management path under index.php/ and reviewing how its CSRF protection affects mobile clients. Clarify the OCS endpoint's supported avatar operations and expected access behavior before estimating the implementation; done means mobile clients can manage avatars through the public endpoint without the current constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100