PR: https://github.com/LimeSurvey/LimeSurvey/pull/1663

Personnaly : i prefer a clean way to extend remote_control via API.

I already have an hacked way (working since years now )

Sample : https://gitlab.com/SondagesPro/RemoteControl/extendRemoteControl
And a branch : https://gitlab.com/SondagesPro/RemoteControl/extendRemoteControl/-/tree/exportReponseFiltered

Thank you for pointing out the possibility of extending RemoteControl via API, which is a really interesting approach.

However, I did not originally intend to request a feature extension of the RemoteControl 2 API.

For the mentioned requirements it would be sufficient to have the functions in LimesurveyApi.php:

When a federated user logs in, the OIDC provider supplies a set of attributes in the login event, including the user's Virtual Organization (VO). The plugins then creates the user group per each VO the federated user belongs to and adds/removes the local representation of the user to the group. This is to isolate the VO's and its members from each other on a given level.

Nevertheless, it would generally be helpful to have support for user groups in the RemoteControl 2 API.

Calling the "external" API from within the plugin is one approach when there is nothing else, my concern here is that it slows things down quite a bit.

I understand your pointg of view.

Mine is

1. current LimeSurvey core dev can not really construct new featire since they are only in bug fixing
2. We have another RC update pull request : https://github.com/LimeSurvey/LimeSurvey/pull/1660
3. remotecontrol_handle have mote than 3000 lines
4. To have your feature in core : you have to wait some week (or month) before it was merged.

With a plugin event (or another system) : no need to wait, more easy to create/adapt new fuinction, LimeSurey core can stray lighter.

Thank you for further clarifying this issue. In general, I agree that this is an appropriate solution regarding extensions of RemoteControl.

However, for my use case, which admittedly could be somehow special and therefore not of general interest, I do not see much benefit in avoiding the "direct use of classes found in the source code" by moving it to another location. So I could just be as happy with my plugin as it is and leave the functions I have provided as PR in it. If you think differently about it, please let me know.

I think I was a bit misled by the phrase "New functions can be added to the API object on request" in the plugins-advanced documentation.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=31535

Fix committed to 3.x-LTS branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=31573