Switch from services to engage ui url #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #8 ,
Description
please have a look at the issue's description
What it does
We now use the
getOrgEngageUIUrl
method from opencast libray base api, which uses the/api/info/organization/properties/engageuiurl
in the background.This means for those institutions that are going to use this plugin while they have multinode opencast setup + lti, they need to do the following:
For old (Upgrades) and new (fresh installs) users:
The Opencast API User must get the role
ROLE_UI_EVENTS_EMBEDDING_CODE_VIEW
in order to access that endpoint.Of course it is a default role that Opencast is shipped with, if you have changed the roles of that endpoint in opencast under
/etc/opencast/security/mh_default_org.xml
you must give that role to the API user!For old user (Upgrades)
It you are reaching here and it is relavant to you, that means your Opencast API User has already have the role
ROLE_GROUP_MH_DEFAULT_ORG_SYSTEM_ADMINS
.Thsi role is no longer needed here, you could remove it from the role list, only if the sole purpose was to use this plugin!
To TEST
It is a very complicated scenario: