I beg your pardon, but there's nothing to workaround about.
To authenticate an OSX machine in a LDAP domain something must be configured on both sides..
I don't know the OSX's one, but I'm quite sure that on NS side there must be an addictional schema in ldap and that TLS must be used, otherwise there's no access to username/passwords (and so you've to deal with certificates and so on); it's not trivial at all.
moreover, the link you posted is referred to a quite old OSX release and a different situation: in that case an OSX client is trying to authenticate itself on another OSX open directory ldap, which is a bit different from openldap and that needs kerberos (just like AD); to work with NS' ldap, you don't need kerberos (at least, linux clients don't need it to use ldap authentication)
regarding logs: they are useless, but it seems you don't understand..
to understand the situation, think about the client speaking in english and asking for credentials to NS, which is a native chinese speaker.. no automatic translation in the middle, so, on both sides, you can only find something that souds like "I asked, no one answered" and "I hear something, but can't understand what it was"
is it clearer now?
instead of asking for logs, install a vitual NS in bridged mode on your mac and try yourself, but I advise you it won't be easy
finally: remembering what you told about developers documentation for dummies and the answer you got from @stephdl (something like "if you aren't driven by curiosity, you won't never be a developer"), I notice that in this case, where you CAN do some tests on your own and help OP, you are not.. I have no mac here and I won't deal at all with dowloading it in any way just to try, but the request coming from OP is interesting, and who has the possibility to make some tests, should really dive into.
all, as usual, IMVHO