Feature #19335

Allow setting user account settings to read-only fields (especially when using LDAP)

Added by James H about 7 years ago. Updated about 7 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Permissions and roles
Target version:-


I would like the ability to be able to set specific user account information fields to read-only.
This will be particularly useful for when using LDAP to handle the user's account & details.

Currently, I am using LDAP to handle user account creation and log-ins.
This works great, but one thing I have noticed is that even when using LDAP, it allows the user to change any of their user account information fields.

This could be a good thing, but in my case, when users start changing their login or their email address and parts of my application/system requires their login and/or their email address to be the same as whats in LDAP, it is horrible.

Also, another problem is when the user is able to change their email address to whatever they like, and they enter a wrong address (whether purposefully or not). This causes the email notifications to not work correctly for things like project News because one of the member email addresses is invalid.

Related issues

Related to Redmine - Defect #8157: Redmine do not send notification emails if a recipients e... Closed


#1 Updated by James H about 7 years ago

Loosely related to the email notifications problems in #17318 which is a duplicate of #8157

The email notifications problem is a big driving factor for me wanting to get this fixed.

#2 Updated by Toshi MARUYAMA about 7 years ago

  • Related to Defect #8157: Redmine do not send notification emails if a recipients email address is not valid added

Also available in: Atom PDF