[Date Prev][Date Next] [Chronological] [Thread] [Top]

multiple password attributes...

Is anyone using a LDAP in an authentication environment with
multiple service based password fields?

I want a NIS type schema for authenticating access to services. I could
reproduce the same tree per service, each with duplicated user details
including the password field, but that seems wasteful. I'd like to have
say 3 password attributes, each for a different service.

How does OpenLDAP know which attribute to check the bind credentials