As such it is possible for user to set a user name which is already being used.
And if that happens, all the login attempts with any user with that user name fails.
Users should not be allowed to edit User name from My Preference page and there should be a check for duplicate User name.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Nilay KhatriTitle changed from **User can edit hiw profile through My Preference and can set duplicate username ** to **User can edit profile through My Preference and can set duplicate username **
Title changed from **User can edit hiw profile through My Preference and can set duplicate username ** to **User can edit profile through My Preference and can set duplicate username **
@lord_alan yes that is correct, ajax edit is not working on User name field. But if we enter Edit view then we can change the User name.
This could be problematic in scenarios where we need to address users by some thing uniqueness (Like User name, or Firstname + Lastname, Email etc.). If user could change the details, it could cause Data security issues. As one user could amend its details in a way so that he gets access to other User's data.
This issue is faced by us while customizing comments for a client. We needed a way so that if a certain combination of User detail is present in the field's value then that user must be notified.
But as far as we can see now there seems no such probability.
Confirmed, cannot create a new user with duplicate name.
So summarizing following are the issues:
non-admin user should not be allowed to edit the User name field
if admin user is changing the User name field, duplicate check must happen (though admin user cannot create a new user with duplicate user name he can later edit an existing user and enter duplicate user name)
I think it is a good idea to have the capability to change user names at least for security reasons. What is missing is the user name validation by the save operation to avoid duplicates.
I've noticed when changing the displaytype to 2 in vtiger_field that when you add a new user, the username does not get saved, it appears blank.
I have tried several times to replicate and it happens every time the displaytype is set to 2 in vtiger_field for username.