Closed FriedrichWeinmann closed 4 years ago
It currently considers the full path of a user object to be:
CN=<SamAccountName>,<Path>
This is obviously wrong, as the name property, not the SamAccountName defines its path, leading to issues in cases where the two are not equal.
Proposed changes:
Name
Resolved in 1.3.62
It currently considers the full path of a user object to be:
This is obviously wrong, as the name property, not the SamAccountName defines its path, leading to issues in cases where the two are not equal.
Proposed changes:
Name
to list of supported propertiesName
property will be optional in config input, causing the name to default to the SamAccountName, thereby not invalidating existing configuration.