Opencast user used by Stud.IP #725
Labels
priority:low
tool:opencast
Would be nice if fixed in Opencast directly. :)
type:documentation
type:security
v:3
Everything related to the Stud.IP Opencast Plugin Version 3.x
The documentation about creating a user in Opencast which can be used by Stud.IP contains several weird or misleading statements.
studip-opencast-plugin/INSTALL.md
Lines 208 to 212 in 701056c
opencast_system_account
ceased working”: I know what the meaning behind this is: Don't try using an Opencast user created for HTTP Digest authentication. But given that these can be named however you want, this sentence is only helpful if you already know a bit about Opencast. Opencast generally uses “digest user” to distinguish those from regular uses. Maybe something like this could be a replacement for the current sentences:An Opencast digest user (e.g. used for some capture agents) will not work. If you want to test this, make sure you can use this user to log into Opencast's admin interface.
-Why would
ROLE_ADMIN_UI
be required if the other role already is the global admin role which will effectively bypass any other authentication? Adding any role to someone who already hasROLE_ADMIN
should make no differenceAs a bonus: Does the plug-in really require the maximum amount of privileges you can have in Opencast (
ROLE_ADMIN
)?The text was updated successfully, but these errors were encountered: