AD/LDAP Connection Profile Mapping


the profile mapper in the admin UI of the ad/ldap connector doesn’t seem to do anything for us.
Here you can see how I hardcoded name.familyName to abc because none of my changes had any effect on the user profiles. (I did save)

After this I deleted the user profile from Auth0 and logged in again and saw that the family name of the fresh profile was not abc but the one stored in LDAP under sn. The profile mapping does not seem to have any impact on the profiles.

Any ideas?

Ok, after trying some more I figured out that the service must be restarted to apply these settings.
Is that intentional? I couldn’t find this mentioned anywhere