Incoming SakaiPlus role mapping should ignore institution level roles in a context

Description

When SakaiPlus receives a launch, it should ignore institutional role and only use membership roles like:

The above example is from a person that is a Learner in this class and an Instructor anywhere in Canvas. Oops.

This removes the institutional roles from the default !site.template.lti realm:

Guest, Faculty, Member, Staff, Alumni, ProspectiveStudent, Other, Administrator, Observer

These are server-wide roles not context-level roles and have no value within a context.

Attachments

3

Activity

Show:

Charles R Severance January 16, 2023 at 2:29 PM
Edited

Things indeed look correct in nightly - in the screen shot you uploaded. The key was not to see the additional roles that were deleted.

Andrea Schmidt January 16, 2023 at 2:25 PM

Nevermind the above comment…I just realized that in production it would be very unlikely a Sakai user would launch a SakaiPlus site So for the Sakai side, the roles match your “new” version and my users are assigned “Learner” and “Instructor” roles in the Plus site.

Andrea Schmidt January 16, 2023 at 2:09 PM

Are Learner and Student the same thing? What are the equivalents in Sakai for ContentDeveloper, Manager, Mentor, and Officer? I assume Member is for a project site? Is there way to test the roles without accessing Canvas?

Andrea Schmidt January 16, 2023 at 2:02 PM

Charles R Severance January 16, 2023 at 1:47 PM

it is ready now - it was going to be ready as soon as the database got re-generated. It will work on the qa server once it is merged back and the qa server is reset. But to merge it back - it needs to be verified in master first - which should be ready right now.

Fixed

Details

Priority

23 Status

Merged

Components

Assignee

Reporter

Conversion Script Required

Yes
Created January 6, 2023 at 9:18 PM
Updated January 31, 2023 at 4:50 PM
Resolved January 10, 2023 at 7:43 PM