Stop updating username on login

[jcanning]

Hi All,

I have a need where I am syncing users from AD but the First Name Attribute is not the name i want to use. So with the Sync i update the user name to be the correct username (think something like 'Leonardus' to 'Leo').

This update works fine as i am doing a key/value pair loop to update from a list like so: User.objects.filter(first_name=k).update(first_name=v). However, the issue i am running into is when that user actually logs in, it re-updates the first name to the AD name.

Is there any way to turn that off or specify which attributes to sync upon login?

Here is my configuration:

LDAP_AUTH_URL = 'ldap://server.domain.com'
LDAP_AUTH_FORMAT_USERNAME = "django_python3_ldap.utils.format_username_active_directory"
LDAP_AUTH_ACTIVE_DIRECTORY_DOMAIN = "domain"
LDAP_AUTH_CONNECTION_USERNAME = USER
LDAP_AUTH_CONNECTION_PASSWORD = PASSWORD
LDAP_AUTH_USE_TLS = False
LDAP_AUTH_SEARCH_BASE = "DC=domain,DC=com"

LDAP_AUTH_FORMAT_SEARCH_FILTERS = "appname.utils.custom_format_search_filters"
# nothing special here as this is just specifying groups

LDAP_AUTH_OBJECT_CLASS = "user"
LDAP_AUTH_USER_LOOKUP_FIELDS = ("username",)
LDAP_AUTH_USER_FIELDS = {
    "username": "sAMAccountName",
    "first_name": "givenName",
    "last_name": "sn",
    "email": "mail",
}

Thanks,
jAC

[etianen]

The LDAP_AUTH_USER_FIELDS settings controls the mapping of LDAP fields to Django fields. If you don't want to sync first and last name, remove the "first_name" and "last_name" entries from that setting. If you want to sync them with a different LDAP attribute, change the values for "first_name" and "last_name" to the appropriate LDAP field.

…

On Wed, 24 Mar 2021 at 17:26, John Allan ***@***.***> wrote: Hi All, I have a need where I am syncing users from AD but the First Name Attribute is not the name i want to use. So with the Sync i update the user name to be the correct username (think something like 'Leonardus' to 'Leo'). This update works fine as i am doing a key/value pair loop to update from a list like so: User.objects.filter(first_name=k).update(first_name=v). However, the issue i am running into is when that user actually logs in, it re-updates the first name to the AD name. Is there any way to turn that off or specify which attributes to sync upon login? Here is my configuration: LDAP_AUTH_URL = 'ldap://server.domain.com' LDAP_AUTH_FORMAT_USERNAME = "django_python3_ldap.utils.format_username_active_directory" LDAP_AUTH_ACTIVE_DIRECTORY_DOMAIN = "domain" LDAP_AUTH_CONNECTION_USERNAME = USER LDAP_AUTH_CONNECTION_PASSWORD = PASSWORD LDAP_AUTH_USE_TLS = False LDAP_AUTH_SEARCH_BASE = "DC=domain,DC=com" LDAP_AUTH_FORMAT_SEARCH_FILTERS = "appname.utils.custom_format_search_filters" # nothing special here as this is just specifying groups LDAP_AUTH_OBJECT_CLASS = "user" LDAP_AUTH_USER_LOOKUP_FIELDS = ("username",) LDAP_AUTH_USER_FIELDS = { "username": "sAMAccountName", "first_name": "givenName", "last_name": "sn", "email": "mail", } Thanks, jAC — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#203>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABEKCBAOHXC46TKO2RGWQDTFIODJANCNFSM4ZXWXOUQ> .

[jcanning]

Hi Dave,

That part makes sense but what i was wondering is if there was a way to not overwrite the user name after the first time it is synced? I only have 5 users out of 100 that need their name updated. So removing the first_name field would cause more work in the end.

So for example, just allow the ldap_sync_users command to set the first name and last name when not set anything if they are not synced.

Is something like that possible?

Thanks,
jAC

[etianen]

There's nothing like that built in. Possibly you could make a second settings file with a different LDAP_AUTH_USER_FIELDS file. When calling ldap_sync_users you could use the settings file that syncs name, and when running the app otherwise you use the settings file that does not sync name. The important thing is to always sync a minimum of username, as that's used to correlate the Django users with the ldap database.

…

On Tue, 30 Mar 2021 at 00:59, John Allan ***@***.***> wrote: Hi Dave, That part makes sense but what i was wondering is if there was a way to not overwrite the user name after the first time it is synced? I only have 5 users out of 100 that need their name updated. So removing the first_name field would cause more work in the end. So for example, just allow the ldap_sync_users command to set the first name and last name when not set anything if they are not synced. Is something like that possible? Thanks, jAC — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#203 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABEKCDUYAWTB7LJPXVQCA3TGEH7JANCNFSM4ZXWXOUQ> .

[jcanning]

Ahh that's a good idea. Thanks Dave!