Hi all, I have one question that official documentation and forums don't seem to have an answer for: when creating local (LDS) user objects (not related to userproxy objects from AD) I noticed that each user doesn't have authorization to change
its own password. This is different from Active Directory and it basically forces applications to bind LDS under a different set of (administrative) credentials when a user wants to change his own password.
I'm surprised Microsoft hasn't planned for user objects in LDS to automatically have write permissions on at least certain of their own attributes.. just like AD.
Can this be fixed? It would make for a more secure user editing front-end in our applications..
Thanks a lot,
Sergio
Sergio