Dave Medland-Slater answered on the discussion 'LDAP Authentication FAILURE'
'The login policy needs to be explicit, not all (the manual I think is wrong there). LDAP takes over the explicit usage. If you login with SA, the LDAP TPS authentication still looks you up as if you were explicit, not via LDAP, so you need a 'proper' account to test with. The username you enter is the LANDesk explicit login and the password is the LDAP password that corresponds to the network connection entry. The network connection values are the LDAP distinguished name and in my experience need to be the first entries in the list of authentication strings. Any AD ones need to come after this. Values would be something like ...
I have set the login policy to explicit , but I get the same error message anyway. What I would like to know, is the the Network Login string correct in the Administration component or in the DirectoryServiceAuthenticationConfiguration.xml file?
1 of 1 people found this helpful
I don't think OpenLDAP is a supported platform, which is a bit of a problem. My experience has only been with AD and ED and for those the syntax in the setup guide just works. So as I haven't used OpenLDAP I don't know whether the problem is with the DirectoryServiceAuthenticationConfiguration.xml or the network logins. One thought - have you used some sort of LDAP browser or explorer tool to connect and try to see what values it holds for the various users in the tree?
Thanks for helping out .
I just got it to work ,
I changed the string in the <ServerObject> and know it works
Well done Sweden!