API-driven user management #52
Labels
No labels
admin tools
api
bug
documentation
duplicate
enhancement
feature
help wanted
in progress
internals
invalid
packaging
question
testing
trivial
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: MensBeam/Arsse#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NextCloud provides a user management API based around www-form input and XML output:
https://docs.nextcloud.com/server/11/admin_manual/configuration_user/user_provisioning_api.html
Implementing this protocol should provide effective consistency with a NextCloud News installation, yielding opportunities for code re-use for clients. It also has the advantage of keeping Arsse headless, and as a server-only application.
NextCloud's documentation does not appear to be clear about the user classes which exist and what they mean. While it may make sense to align as much as practical with NextCloud, it probably doesn't make sense to implement absolutely everything.
Note that CommaFeed also provides a JSON-based interface for managing users.
After years of speculation, it seems the Miniflux API will finally make this a reality.
Implemented in
31f0539dc0
.