If the mail attribute is empty in LDAP and then I fill it and re-login on the web UI
(which apparently triggers fetching the account details) it updates the Gitblit user's
mail attribute accordingly, but if I do it the other way around i.e. the LDAP mail
attrib is already filled and I erase it the Gitblit mail attribute will not go away.
I'm pretty sure it's not a cache problem coz the user's LDAP attrib's been empty for
weeks and Gitblit's been restarted several times ever since. The old mail attrib's
still present in Gitblit.
If I delete the mapped Gitblit user and re-login, the user will appear in the Gitblit
user list without the mail address, as it should.
Also, if I add just a simple character to the LDAP mail attrib Gitblit will change
the Gitblit user's mail attrib to that right away. So it seems like an unnecessary
check somewhere in the code.
Reported by email@example.com on 2014-07-02 12:02:09
The text was updated successfully, but these errors were encountered:
Hopefully fixing this for you doesn't generate complaints from other LDAP users. LDAP
is one of the few parts of Gitblit that is a little voodoo for me. I don't run LDAP
and it is sooo flexible/configurable that it is easy to make something work for one
group and break others. :/
This *should* be just a straight-forward fix.
In fact, I think this also affects group membership, i.e. if I remove someone from the
LDAP git admin group, the user remains an admin in Gitblit even after re-login.
But I may be confusing things, I'll have to re-check tomorrow.
Reported by firstname.lastname@example.org on 2014-09-08 18:00:48