Stefan, Yes, you are probably right ... after I use Extended Operations => Modify Password ..., which defines an encryption hash, I can then use the Password Editor.
Which just goes to prove that someone like you with years of experience with ApacheDS, can make better guesses than someone like me, with maybe two hours of experience with the product ... ;-) Just two more notes: Root vs. Non-Root under Linux I tried creating a non-root user -- given that the default ports in the configuration are > 1024, specifically 10389 and 10636 -- but even after changing (I think!) all of the file ownerships and permissions (this is on Linux), I ran into some odd problems with files seeming be created with root permissions, and being unaccessible under the non-root user. It is possible that something kicked-off or started while I was in the middle of making the ownership changes -- although I didn't think so -- but was wonder if running ApacheDS is fully "supported" running under a non-root user (e.g., Linux)? Or is running under root preferred? Or should it really not matter? Nonetheless, I changed back to root, mostly because I like using port 389 for LDAP, but might want to change back to non-root in the future, since running services as root is usually not a good idea. Thanks, Dave. > On Apr 5, 2021, at 11:19 AM, Stefan Seelmann <[email protected]> wrote: > > On 4/5/21 4:49 PM, David Filip wrote: >> Also, when updating the documentation, Extended Operations => Password >> Modify does work successfully for uid=admin, ou=system >> >> And the Password Editor works correctly for other users in ou=system >> >> So it appears to be a problem unique to the admin user. > > More guessing from my side: it may have to do with the fact that the > initial password (secret) is stored as plain text (Studio shows it as > "Plain Text Password"). Once the password is changed and stored in its > hashed form (there is a server-side interceptor that hashes the > password) it's possible to change the password by editing the > userPassword attribute. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
