What was the problem with the user synchronization?
It's hard to tell what could be the underlying problem with updating the user, but it looks like you need to sort out how the user can be updated in the AD. As a side note, you might have an easier time sorting this out after upgrading to version 12 of the CMS, since user management has changed alot.
Hi Ynze. Thanks for your response.
The syncing of user never did work in current AD connection. Changing to a custom ActiveDirectoryMembershipProvider overriding findUser method solved the bit with being able to list AD users in Content Aproval Module, though. But when doing this, the SaveUser action cannot be performed, probably due to access restriction to the ldap user.
Upgrading to 12 is not something we wish to do at this point.
FIrst a little context:
Using a connection to company AD in customer site so users (e g editors and admins) can login into CMS.
Recently added a custom ActiveDirectoryMembershipProvider to that the approval sequence would search users against the AD, instead of the tblSyncedUser, since the syncronization never worked. The custom provider overrides the FindUsersByName method replacing the wildcard character from '%' to '*'. Nothing apart from that.
This however seems to impact when user changes its profile.
For example changing Personal Language (UI Language Settings) under Display Options and hitting Save.
This action results in an error message:
I would guess the Save events tried to save to the AD but the credentials does not have Save-permissions?
Can anyone confirm this and/or have a way forward in resolving this?
Using the latest cms in major version 11.