You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the installation, a new user with the capabilities webservice/rest:use, tool/opencast:externalapi, moodle/user:viewalldetails, moodle/user:viewdetails and moodle/site:accessallgroups has to be created. Then generate a new web service token and add that user to the "Opencast web service" service.
If the set of 5 capabilities from the Opencast documentation is enough, then it should also mention that the warning in Moodle can be ignored.
If there is a real need for these 3 additional capabilities, then the Opencast documentation has to be updated - and it has to be especially checked if Opencast can crash anything in Moodle if we add the moodle/user:update capability to the Opencast user.
In any case, this has to be evaluated on the Moodle side first (that's why I am posting it here and not on opencast.jira.com).
The text was updated successfully, but these errors were encountered:
https://docs.opencast.org/develop/admin/configuration/security.user.moodle/ tells us how to create the Opencast API webservice user in Moodle:
Interestingly, after adding the user to the Opencast web service in Moodle, Moodle tells me at two locations (https://MYMOODLE/admin/webservice/service_functions.php?id= and https://MYMOODLE/admin/settings.php?section=webservicetokens) that the user is missing the additional capabilities moodle/user:viewhiddendetails, moodle/course:useremail, moodle/user:update which seem to be required for core_user_get_users_by_field which is part of the "Opencast web service" set.
If the set of 5 capabilities from the Opencast documentation is enough, then it should also mention that the warning in Moodle can be ignored.
If there is a real need for these 3 additional capabilities, then the Opencast documentation has to be updated - and it has to be especially checked if Opencast can crash anything in Moodle if we add the moodle/user:update capability to the Opencast user.
In any case, this has to be evaluated on the Moodle side first (that's why I am posting it here and not on opencast.jira.com).
The text was updated successfully, but these errors were encountered: