Again, the letter was meant as CONSTRUCTIVE, do not be defensive. Yes, I read it numerous times, was the number exactly 10, more or less, that is not the question.
It turned out to be on page 19 that the bind for something as an attribute versus a CN would require a field of something like "(cn, uid)" not just "cn" I'm sorry but you'd better realize quickly that a 100 pages is trivial. When you hit 10,000 and it's professionally templated, easily understood, cross-referenced, etc. and CONSTANTLY updated from revision to revision of the software, then you've achieved proper documentation. To give you an idea, I'm, presently, starting my own business venture. I needed an Exchange replacement for a SMALL part of what I'm doing. My document of installing and configuring SOGo is almost 40 pages alone. It does not go into the internals, nor does it go into nuances. It's a simple directional flow document. (A flowchart put into words) For the existing 12 products (and more coming) and their integration with each as well as standalone..... I have approximately 700 pages of documentation. Those pages are just for installation and integration. So, yes, I am extremely detail oriented. I NEED people to want my company and it's product offerings. If you feel that someone like me shouldn't have issues with your product installation, configuration and have a true understanding then you need to fix the documentation. If you need to have someone who isn't a professional at this perform an installation, then I stand by my statement, the documentation is horrid. It's your choice to fix it or not. *shrug* It doesn't matter to me, I can always get around things and go low-level with trace/truss to find out what's going on and turn on major debugging. The rest of the people will just throw their hands up in frustration and walk away. Is that what you want? The world owned by MS Exchange or Zimbra or something else? I'm a seasoned person (yeah, 50 y.o.) and I don't expect people to understand all the times in tech history where superior tech was beat out by better/faster adoption. However, if anyone remembers Sony's Beta Max format versus VHS.... Beta was vastly superior, however, higher cost for BETA and better marketing for VHS, BETA died. VHS got adopted in droves. .... and don't even get me started on Microsoft Windows versus Unix...... :-) Cheers! P. ________________________________ From: Ludovic Marcotte <[email protected]> To: [email protected] Sent: Saturday, July 6, 2013 2:34 PM Subject: Re: [SOGo] Dear progammers and architects On 2013-07-06 1:05 PM, Paul Pathiakis wrote: I'm attempting to get this ported over to FreeBSD as I believe it to be a superior product. However, if one little thing that I read over 10 times had to be, finally, pointed out by Jean (I believe), as to what I was looking for, that says something very, very bad. Have you really read it ten times? This is clearly explained on pages 17 and 18 from the doc - the very first page on LDAP authentication. Here it is: For certain LDAP sources, SOGo also supports indirect binds for user authentication. Here is an example : SOGoUserSources = ( { type = ldap; CNFieldName = cn; IDFieldName = cn; UIDFieldName = sAMAccountName; baseDN = "cn=Users,dc=acme,dc=com"; bindDN = "cn=sogo,cn=Users,dc=acme,dc=com"; bindFields = (sAMAccountName); bindPassword = qwerty; canAuthenticate = YES; displayName = "Active Directory"; hostname = ldap://10.0.0.1:389; id = directory; isAddressBook = YES; } ); In this example, SOGo will use an indirect bind by first determining the user DN. That value is found by doing a search on the fields specified in bindFields. Most of the time, there will be only one field but it is possible to specify more in the form of an array (for example, bindFields = (sAMAccountName, cn) ). When using multiple fields, only one of the fields needs to match the login name. In the above example, when a user logs in, the login will be checked against the sAMAccountName entry in all the user cards, and once this card is found, the user DN of this card will be used for checking the user's password. If have ideas on how to improve the doc, share them. We've written about 100 pages of documentation on SOGo. Saying it is horrid is a pretty impressive statement. -- Ludovic Marcotte [email protected] :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- [email protected] https://inverse.ca/sogo/lists
