Net::Ldap pb with SASL under multidomain MS Lan.
jean-charles Gibier
I had to connect several Ldap servers under MS Lan via Net::Ldap module
My Attempts fails and I receive an "invalid credential".
I suspect that SASL layer does not handle this service as SSPI does.
Can someone confirm ?
Is there any other solution to do that ?
jean-charles Gibier
"jean-charles Gibier" <jeancharl...@free.fr.invalid> a écrit dans le
message de news: 48849f97$0$24362$426a...@news.free.fr...
> Hello,
>
> I had to connect several Ldap servers under MS Lan via Net::Ldap module
I forgot :
several ldap servers "located in external ms domains"
Leon Timmermans
Really, we can't help you if you give that little information. Can you
give a little more. A code sample, some information about how the AD is
configured, etc...
Leon Timmermans
Jean-Charles Gibier
I am sorry. I think I am a little disconnected with the topic because my
problem is not really in the code. The object is definitely well
instantiated and I can bind the AD server as far the "ldap user" is in
the same domain.
But if I want "bind" an "external" one I can't. I think this is due to
the limitation of the authentication layer used by the module.
I just want to know if i am right and if maybe someone is aware of that.
Thrill5
"Jean-Charles Gibier" <j-c.g...@wanadoo.withoutthis.fr.invalid> wrote in
message news:4884ea91$0$963$ba4a...@news.orange.fr...
If you want to bind to an external LDAP server, you need the appropriate
credentials. The reason you can bind to the "local" LDAP server is because
you are probably using that local users credentials to bind and read that
users objects. When you try to bind to an external LDAP server with that
local users credentials it fails probably because that user doesn't have
authority to a) bind to the server, or b) has any rights to read any of the
objects stored on it.