Names and Role Provisioning Services (NRPS)

If you need any help in filling out this wiki page, please have a look at the page ’How To Suggest A New Feature’. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

LTI launches tell each side only about the user who launches. An external tool in ILIAS does not know the other members of the course, and ILIAS as a tool does not know the members of the course at the platform until each one launches: an instructor cannot prepare anything for learners who have not entered yet.

2 Conceptual Summary

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

Both forms get the checkbox "Names and Role Provisioning Services", for LTI Advantage only and off by default, also for existing tools and platforms. When a tool registers in ILIAS through Dynamic Registration, the checkbox is set if the tool asks for the service.

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

None. The checkboxes are KS elements.

4 Additional Information

4.1 Involved Authorities

Authority to Sign off on Conceptual Changes: Díaz, Saúl [sdiaz]
Authority to Sign off Code Changes: Díaz, Saúl [sdiaz]

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

4.3 Privacy

As Platform, the tool receives each member as a launch would describe the user, under the same privacy settings of the tool ("User identification", "User name"). With a random user id per object, only members who launched the object are listed. ILIAS stores nothing for it.

As Tool, ILIAS creates an account for each active member without one, with the user id, name and email the platform sends, even for members who never launch ILIAS. This is why it has to be activated per platform.

The data is described in the PRIVACY.md of the LTI component. Until the LTI rework is merged into the ILIAS repository, this link points to the branch trunk_LTI_rework of the SURLABS fork.

4.4 Security

As Platform, the list is only given to a tool with the service activated, with an access token of LTI Advantage for that tool, and only for a course or group that holds an object of that tool. It is read-only. As Tool, the list is read with an access token from the URL the platform gives in the launch, and only active members get roles, only those of the release.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Díaz, Saúl [sdiaz]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.