but it seems to succeed whatever the password I'm providing :-(
How to simply assess the binding really occured ?
Do I need to start doing stuff with the "l" object to catch an error
and realize I'm not in fact connected : that's my current workaround
but I'm not very proud of it...
Gnome - autofs nfs home directories ... Thanks to the help I got in this list my LDAP authentication now works ... get authenticated by the LDAP server and autofs ... Everything works fine providing a user doesn't log on to two machines at ... (Fedora)
Re: Sun Java System Directory Server Authentication ... Note that I'm not picking on you, I largely following your reasoning and that I don't agree ... The same goes for LDAP, at the core each LDAP server handles the LDAP protocol, but that ... Solaris LDAP to handle NTLM authentication.... network "authentication" as used when binding against an LDAP server is meant to 1) validate ... (microsoft.public.dotnet.languages.csharp)
Re: USE of ADFS ... For pure LDAP authentication,... controller in the forest to authenticate a user in ANY domain in the forest. ... unless you specify that domains ldap server.... (microsoft.public.windows.server.active_directory)
Re: AD Auth for standalone ISA in DMZ ... you can't use LDAP for access rules.... until you change the authentication method of select a different user ... Under Specify RADIUS and LDAP Servers,... (microsoft.public.isa.configuration)
Re: pam_ldap and password management and rsh/ssh without password ... > authentication that doesn't require a password will fail. ... > that accounts may be expired (via ldap).... pam_ldap has to actually be able to bind to the ldap server as the user ... disadvantage to this is that then the clients are managing the password ... (comp.unix.solaris)
