Hello,
I have been testing sporadically openldap two years now, including many advanced features, sql, ppolicy, etc we are currently evaluating openldap along with redhat's 389 for enterprise use as RBAC, on which we will built upon our existing infrastructure. We want to have full password policy enabled, in order to meet requirements for passing SOX (Sarbanes Oxley) compliance. 389's documentation is lousy, I haven't tried anything exotic (sql, etc) with it, the reason we are looking at it is because it is favored by kolab.org and likely to come as standard in future kolab versions. So I would like your opinion on this. Pros/Cons to choose openldap or 389 directory server as our long term strategic decision?
Achilleas Mantzios wrote:
389's documentation is lousy, I haven't tried anything exotic (sql, etc) with it, the reason we are looking at it is because it is favored by kolab.org and likely to come as standard in future kolab versions.
Is there a kolab.org document pointing out the reasons why they want to go that route? It would be likely helpful for answering particular points instead of endless pro/con lists.
In general: When comparing things/systems/whatever it's pretty hard to avoid the bias based on personal preferences. So the place where you ask always will result in biased responses.
Ciao, Michael.
On 19/04/2016 12:01, Michael Ströder wrote:
In general: When comparing things/systems/whatever it's pretty hard to avoid the bias based on personal preferences. So the place where you ask always will result in biased responses.
That's a given, I know, but having been following this community for some 2 years, I feel/trust that the answers will be as technical and unbiased as it can get. Kolab docos suck and their future roadmap is unclear so I didn't bother bringing this in. If it depended solely on me we would be already migrating to/deploying openladp by now.
Ciao, Michael.
openldap-technical@openldap.org
-
Achilleas Mantzios -
Michael Ströder