On 04/02/2013 02:02 PM, Vesa Alho wrote:
I have a need to create new attribute where to store password in
different hash than used in 389ds. This is because 3rd party does not
support our SSHA-512.
You can configure the password policy to use a different
I'm planning to add an attribute, but a couple of basic
1. I have understood it's usually good to avoid creating custom
attributes? So is it a good practise to use some unused attribute for
this kind of purpose, for example I found "usercertificate".
wouldn't think so, if you need a custom attribute, you should
properly define and use it, just using an other attribute will be confusing
2. What is the best way to add new attribute to already existing
entries, create a script with ldapmodify commands?
-Mr. Vesa Alho
389 users mailing list