Hello All,
We've been running for a long time with Microsoft LDAP. I can tell you
Microsoft has it's own LDAP standard. It returns all of their attribute
values with a 'null termination' character. By doing some chopping of the
found LDAP attributes you'll see that your perfect password will match
again, and your connection should be fine.
We've been using LDAPSDK as our LDAP Authentication module (historical
reasons) and by entering
chop($entry->{userpassword}[0]);
at about line 219 (version 2.16.1) you would do fine. If you have any other
attribute you're going to check you should chop them also.
If you're going to do LDAP authentication with another module (LDAP2) would
you be so kind if you've got it working to give me the location of the
necessary changes? In the future I would like to move to this module but I
haven't had any time to get to this :-(.
Good luck with it,
Karel van der Velden
> -----Oorspronkelijk bericht-----
> Van: Jeremy Gault [SMTP:[EMAIL PROTECTED]]
> Verzonden: maandag 28 augustus 2000 16:39
> Aan: Jason Lim
> CC: [EMAIL PROTECTED]
> Onderwerp: Re: (RADIATOR) Microsoft LDAP with radiator
>
> Jason,
>
> Well, I'm assuming that the error was returned when the program
> actually tried to connect() to the LDAP server. The "Connection refused"
> error *usually* means that nothing is listening on that port (i.e. there
> is no LDAP process running.) If it is, you may want to check on any sort
> of firewalling between you and it. You CAN set a firewall to return that
> error, but I personally don't recommend it. Returning that error (vs.
> just dropping the packet) requires sending back a packet, which uses up
> bandwidth, and could lead to some sort of DoS hole.
>
> Get with the admin of the LDAP server, and see if it is actually
> running. Check on any firewall / filters between you and it. Good luck.
> :) (I've never messed with LDAP -- just TCP/IP.)
>
>
> Thus spake Jason Lim ([EMAIL PROTECTED]):
>
> => Hi all
> =>
> => I am trying to get the radiator to work with Micrsoft LDAP server. I
> => cannot even establish LDAP connection with the server when the command
> is
> => used at the radiator:
> =>
> => prompr> ldapsearch -h xx.xx.xx.xx filter
> => xx.xx.xx.xx : Connection refused
> =>
> =>
> => I keep getting connection refuse. I've check with the LDAP
> => administrator which said that there is not access restriction to this
> LDAP
> => server besides putting in the administrator/password.
> =>
> => I am really not familiar with LDAP server. Is there any configuration
> => needed on the LDAP end ? Also, are there any other essential
> => informations to be in the ldap/radiator config file ?
> =>
> => Thank you very much
> =>
> => Regards
> => Jason
> =>
> =>
> =>
> => ===
> => Archive at http://www.starport.net/~radiator/
> => Announcements on [EMAIL PROTECTED]
> => To unsubscribe, email '[EMAIL PROTECTED]' with
> => 'unsubscribe radiator' in the body of the message.
>
> --
> Jeremy Gault <[EMAIL PROTECTED]> - UNIX Systems Administrator
> WingNET Internet Services (web site @ http://www.wingnet.net/ )
> PGP Public Key @ http://www.wingnet.net/~jgault/pgpkey.txt
> (423) 559-5465 (voice) / (423) 559-5444 (fax)
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
