This attribute name is used only to perform password update (change). Authentication is done directly against LDAP server using user credentials, not by checking and comparing password value. If you want to use different attribute to store password check if your LDAP server enables this.
Hi Bdaw, thanks for your reply... But still i'm getting confusion... if my attribute my-pwd is used only for updating the existed password, then from where jboss is getting the credentials(because i'm using ldap, so from ldap only jboss checks the password...?) to chek the valid user or not....?
can you clear it again..
When user logs in he enter the password. Then the credentials are passed to the LDAP server to validate them (portal tries to create ldap connection using them). At any stage portal doesn't read the password attribute value from LDAP. The main difference with the DB is that portal reads the hash of the password from database table to validate it.
Hi bdaw, thanks for ur fast reply..
the same .ldif file is working with other applications where the authintication has done from ldap. But if i user the same .ldif for jboss portal then only i'm facing this prob... and one more doubt in my .ldif file i don't have any roles like User,Admin... then how can i assign the Admin Role permissions to my company specific role and as well as users.......?