Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opencast user used by Stud.IP #725

Open
lkiesow opened this issue Jun 5, 2023 · 0 comments
Open

Opencast user used by Stud.IP #725

lkiesow opened this issue Jun 5, 2023 · 0 comments
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

Comments

@lkiesow
Copy link
Contributor

lkiesow commented Jun 5, 2023

The documentation about creating a user in Opencast which can be used by Stud.IP contains several weird or misleading statements.

This plugin requires a front end user account to connect to Opencast; create one or use an existing one.
`matterhorn_system_account` and `opencast_system_account` ceased working!
The frontend user needs to following roles:
`ROLE_ADMIN`, `ROLE_ADMIN_UI`

  • Wording: Use “frontend user” or “front end user”. Not both
  • “[…] 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:
    • This plugin requires a user account to connect to Opencast via HTTP Basic authentication; create one or use an existing one.
      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 has ROLE_ADMIN should make no difference

As a bonus: Does the plug-in really require the maximum amount of privileges you can have in Opencast (ROLE_ADMIN)?

@lkiesow lkiesow added v:3 Everything related to the Stud.IP Opencast Plugin Version 3.x type:documentation tool:opencast Would be nice if fixed in Opencast directly. :) priority:low type:security labels Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant