Avoid multiple Accounts per User

1 Requirements

In a company it can get problematic if users have more than one account. Therefore we propose the following measures:
 
 
 

1.1 Merging „Forgot your password?“ „Forgot your username?“

Requesting a new password must be easier than creating a new account. If someone forgets their login information there are also two requests necessary if only one account exists. This is not user friendly.

There is an E-mail-field and an optional Login-field. If the Login-Field  is empty and there is more than one account, the E-mail with the username will be sent. Otherwise the E-mail with the password will be sent. This E-mail always contains the username.

1.2 Preventing registration if the personal number or the E-mail already exists

For the self-registration it is possible to define fields that have to be unique, for example the personal (matriculation) number or the E-mail.

1.3 Coupling usernames

Usernames can be coupled with an other field, for example the personal number (matriculation) or the E-mal adress. The coupling primarily consists of masks for the User; two fields remain internal; in the administration it is possible to ignore the coupling.
Moreover, the coupling with the E-mail adress makes it is possible for the username to consist only of a part of the E-mail adress (before the @).
In this way, the user must not remember a separate different username. 

1.4 Initial password

At the registration by an administrator, the password can additionally be saved as cleartext. This also enables the user to be later informed via login data, for example, when he is informed about the allocation to a course, he can also receive his login data.
At the first login the initialy chosen password must be changed.
If the user never logged in, his stored password is send by the Password-Assistance.

2 Additional Information

• Idea / concept: Alexander Follert, alexander.follert@zinal-consulting.de
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Zenzen, Enrico [ezenzen], 18 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

4 Implementation

Point 1.1 is implemented with a few lines in the file class.ilPasswordAssistanceGUI.php. 
In addition, the mail texts need to be adjusted and the link on the login page. Thats it.