Skip to content

fix: Allow accessing some admin endpoints to admins that can not use Talk - #18107

Merged
danxuliu merged 2 commits into
mainfrom
allow-accessing-signaling-settings-to-admins-that-can-not-use-talk
May 27, 2026
Merged

fix: Allow accessing some admin endpoints to admins that can not use Talk#18107
danxuliu merged 2 commits into
mainfrom
allow-accessing-signaling-settings-to-admins-that-can-not-use-talk

Conversation

@danxuliu

@danxuliu danxuliu commented May 25, 2026

Copy link
Copy Markdown
Member

Follow up to #8330 and #13973

Since Talk 21 the connection check for the signaling server in Talk administration settings fetches the signaling settings, so admins should be allowed to access the endpoint even if they do not belong to any of the groups allowed to use Talk.

Similarly, Talk administration settings fetches the list of all bots, so that endpoint should be allowed too.

How to test (scenario 1)

  • Log in as an admin
  • Open the Account settings and create a group
  • Open Talk administration settings
  • Configure a signaling server; the check should succeed
  • Limit using Talk to the created group
  • Perform again the connection check of the signaling server

Result with this pull request

The connection check still succeeds and returns the signaling server information

Result without this pull request

The connection check now fails with Error: unknown error occurred; in the Network tab of the browser it can be seen that the request to ocs/v2.php/apps/spreed/api/v3/signaling/settings?token= fails with 403 Forbidden and the message Can not use Talk in the response.

How to test (scenario 2)

  • Log in as an admin
  • Open the Account settings and create a group
  • Open Talk administration settings
  • Limit using Talk to the created group
  • Open the Network tab in the developer tools of the browser
  • Reload the page

Result with this pull request

The request to ocs/v2.php/apps/spreed/api/v1/bot/admin succeeds

Result without this pull request

The request to ocs/v2.php/apps/spreed/api/v1/bot/admin fails with 403 Forbidden and the message Can not use Talk in the response.

Since Talk 21 the connection check for the signaling server in Talk
administration settings fetches the signaling settings, so admins should
be allowed to access the endpoint even if they do not belong to any of
the groups allowed to use Talk.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@danxuliu danxuliu added this to the ⛅ Next Major (35) milestone May 25, 2026
@danxuliu danxuliu added bug regression feature: settings ⚙️ Settings and config related issues labels May 25, 2026
@danxuliu

Copy link
Copy Markdown
Member Author

/backport to stable34 please

@danxuliu

Copy link
Copy Markdown
Member Author

/backport to stable33 please

@danxuliu

Copy link
Copy Markdown
Member Author

/backport to stable32 please

Talk administration settings fetches the list of all bots, so admins
should be allowed to access the endpoint even if they do not belong to
any of the groups allowed to use Talk.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@danxuliu danxuliu changed the title fix: Allow accessing signaling settings to admins that can not use Talk fix: Allow accessing some admin endpoints to admins that can not use Talk May 27, 2026
@danxuliu
danxuliu marked this pull request as ready for review May 27, 2026 06:36
@danxuliu
danxuliu requested a review from Antreesy May 27, 2026 06:36

@Antreesy Antreesy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested, change sounds valid!

@danxuliu
danxuliu merged commit a1e457f into main May 27, 2026
81 checks passed
@danxuliu
danxuliu deleted the allow-accessing-signaling-settings-to-admins-that-can-not-use-talk branch May 27, 2026 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug feature: settings ⚙️ Settings and config related issues regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants