New Captcha Implementation for Self-Registration

1 Initial Problem

There is currently no option in ILIAS to protect self-registration (without additional confirmation mechanisms by third parties) with a captcha.

2 Conceptual Summary

A "Captcha" form element is to be introduced to ensure that entries are not made using a bot. An initial application for this is to be introduced in the registration form. Others are also possible.

3 User Interface Modifications

3.1 List of Affected Views

• Form of Self-Registration

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

A new "Captcha" form element is to be introduced and used.

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

Nothing specific.

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: Samoila, Oliver [oliver.samoila], Schenk, Ralf [rschenk], 
• Maintainer: Seeland, Per Pascal [PerPascalSeeland], Jansen, Michael [mjansen],
• 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}.