If you connect with a user which have access to the userPassword
property, you can add "userPassword" to the "jndi.search.attributes"
parameter to the store. This should expose the password as <userPassword
xmlns="LDAP:">password</userPassword> .
Honoré David wrote:
This is more a LDAP philosophy problem. The permissions on ldap servers
look often like that :
anonymous connection can perform authentification.
and only the user can read-write his userPassword property.
then if you want to expose password, you have two solutions.
- Slide connect with a ldap administrator login which have read
access to passwords (security problem .. ?)
- When a the properties of user "/users/john" is required, create
a
new connection to the ldap with the user john ... But ... this is not
possible because you do not have any credential (password) for john.
The real question is "do you really need to expose password in webdav
properties ?"
note : the password in ldap are generally stored encrypted.
Jo wrote:
Hi all,
The documentation tells that JNDIPrincipalStore does not expose password. I
am wondering if there is a certain reason (design philosophy) for this. I am
thinking of implementing one that exposes password and would like to know
whether there is a reason for not doing it.
Thanks in advance for your input.
Jo.-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Antivirus avast! : message Entrant sain.
Base de donnees virale (VPS) : 0526-2, 29/06/2005
Analyse le : 30/06/2005 9:18:17
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Antivirus avast! : message Entrant sain.
Base de donnees virale (VPS) : 0526-2, 29/06/2005
Analyse le : 30/06/2005 9:49:22
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
