nextcloud / nextcloud/notify_push
Update Readme to reflect incompatibility with Client Certificate authentication
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
Feature request
Which Nextcloud Version are you currently using:
30.0.4
Is your feature request related to a problem? Please describe.
Related to the corresponding issue over at the desktop client repo.
Describe the solution you'd like
Add a mention in the readme that specifies notify_push can’t be used with a Nextcloud behind a webserver using client certificates authentication.
Describe alternatives you've considered
Reverting back to polling.
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 in the repository README and review the linked desktop-client issue for the stated incompatibility. Done when the README clearly says notify_push cannot be used behind a webserver with client-certificate authentication and the polling alternative remains understandable.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100