Skip to content

Opencast user used by Stud.IP #725

Open
@lkiesow

Description

@lkiesow

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)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions