Reveal feature for password in Course and Group

1 Initial Problem

When a course or group is password-protected, users are asked to enter the password before accessing the object. Currently, the user cannot reveal the password they are entering; instead, only a placeholder * is shown for each character entered into the textbox. This creates problems, especially for multilingual students who may have activated multiple languages in their operating system that don't align with their keyboard layout, leading them to accidentally enter the wrong characters without noticing. This can be problematic especially in exam situations (which we use both the course and the group objects for), when students are nervous and under pressure and therefore not in problem-solving mode, particularly regarding the IT they're using.

2 Conceptual Summary

This issue could easily be fixed by integrating the reveal feature (identical to the one used for loggin in via switch) into these password requests. The user could click on the eye-closed/open glyph to see the password and realize that they've entered a wrong character (and fix it), which otherwise they would not be able to figure out so easily.

3 User Interface Modifications

3.1 List of Affected Views

• Course - Password request
• Group - Password request

3.2 User Interface Details

For both views, add an eye-closed/open glyph next to the input text box. Clicking the "open" glyph will reveal the password characters, clicking the "closed" glyph hides it.

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Weber, Jens [jens.weber] / Thiel, Anja [athiel]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

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

Approval

Approved at {date} by {user}.