Add domain users to conversations via API
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: (see administration page)
NextCloud version: 30.0.6.
Talk vesrion: 20.1.4
Is your feature request related to a problem? Please describe.
I have set up a Powershell script to manage conversation participants via domain groups via API. However, this only works for local users and does not work for users synced via Active Directory. However, you can add users from Active Directory from the NextCloud interface. The query to add participants is:
Invoke-RestMethod -Method Post -Headers $Headers -Uri "$CloudBaseURL/ocs/v2.php/apps/spreed/api/v4/room/$NCTalkGroupToken/participants" -Body @{newParticipant="XXXXXXXXXX";source="users"}
When specifying domain users by login/mailbox, the API returns 404; when specifying a local administrator account, the request is processed correctly and the new participant joins the conversation.
Describe the solution you'd like
Ability to add Active Directory users to conversations via API.
Describe alternatives you've considered
No.
Additional context
No.
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 at the Talk participants API endpoint named in the report and compare its behavior with the Nextcloud interface path that can add Active Directory users. Done means the API accepts a domain-synced user identifier and adds that user to the conversation instead of returning the reported 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100