Restricting the update of Agile users in field level when integrated with LDAP
We have built integration between Agile and Active Directory to synchronise user information. I understand when we user ‘refresh user from LDAP directpry’ button it pulls information of users from defined LDAP server. But integrated fields are locked in Agile as it does not allow for modification in agile. There is a property in agile.properties which will allow keeping below fields in unlocked mode
Firstname,Lastname and Email
But after modifying Lastname from some other source in Agile, when there is refresh happens from AD, this will be overwritten. How can we control these? Appreciate if any help in this.
Hi,
These fields are updated automatically daily (over the night by default but it should not be possible to change this behavior or manually from the java client) so if you make them editabled, then the values will be overwritten. So why do you need to update them in Agile if then the LDAP will overwite them? For this reason there is no way to make them enabled.
If you want to don’t update them from LDAP, you have to remove them from the Field Mapping in the LDAP section of java client.
Thanka Antonio. Here, LAST_NAME does not require to be in sync with LDAP and it gets updated with Title Info as well in order to differentiate users easily during approval process from some other source. But in LDAP mapping, there is no way we can remove the mapping of below fields, but we can define new mapping along with these
UserID
First Name
Last Name
Password
Email Address
Title
Work Phone
Mobile Phone
Fax Number
So my requirement is to control LAST_NAME update, is there anyway we can do this?
You should not allow access of the field to the user rather only allow access to the process that is updating the fields from AD.
