On 22/11/2013 12:08 p.m., Brig wrote:
Sounds like good advice!
'squidauth' was just an example I was using for this forum. We have two AD
accounts that we have created for these kinds of authentications so I cannot
just easily go change the passwords yet I can request a new account.
Thx but that did not change anything. I first tried changing all single
quotes to double quotes and had same effect. Then based on your comment
about white space I removed all quotes and relied on white space and still
no change.
I have tried every solution I can find on the Internet w/o any
On Wed, Nov 20, 2013 at 09:28:05AM -0800, Brig wrote:
Hi Peter,
Thx for the replies! Your names sounds familiar, were you on the Squid
project like 18 yrs ago? My first Squid project was back then when I used it
to develop a load balancer and I wonder if we corresponded back then?
Anyway
Sounds like good advice!
'squidauth' was just an example I was using for this forum. We have two AD
accounts that we have created for these kinds of authentications so I cannot
just easily go change the passwords yet I can request a new account.
Both of those accounts though have long complex
Hi Peter,
Thx for the replies! Your names sounds familiar, were you on the Squid
project like 18 yrs ago? My first Squid project was back then when I used it
to develop a load balancer and I wonder if we corresponded back then?
Anyway here is the results of the four commands you asked me to
Hi
Which version of squid do you use?
Which os do you use for squid?
Which version of AD do you use?
Is it a ssl ldap?
Thanks.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Cannot-get-basic-ldap-auth-to-work-with-AD-tp4663282p4663404.html
Sent from the
Hi Andrey,
Ubuntu 11.04
Squid 3.3.10 (compiled natively on Ubuntu 11.04)
AD Version: 5.2.3790.3959 (would not surprise me if this AD version is out
of date)
No SSL
I am not really an M$ guy so I do not know a whole lot about the AD side of
it except that I am finding it extremely difficult to
Ok so you have Windows Server 2003 R2.
Do you have all updates installed on windows server?
what shows netstat -aon in cmd?
is there port 389 open?
3.3.10 should work... Did you build it by yourself?
--
View this message in context:
Yes I compiled Squid myself on Ubuntu.
Our SA is pretty good so I would expect he has installed all the updates on
the M$ machine.
Not sure why you need netstat cuz as far as I can tell based on the results
of test #3 and #4 above with ldapsearch it appears that AD is working and I
can get
Ok hmm...
One more thing, did you follow this one:
http://wiki.squid-cache.org/ConfigExamples/Authenticate/Ldap#Windows_2003_Active_Directory_adjustments
Because I use now the U13.10 version with Ubuntu's Squid 3.3.8 from
repository, and Windows 2008 R2 AD. It is working good. However, as far as
Thx for the feedback ideas!
I realize 11.04 is old and in fact I was going to EoL this server since it
is old yet then I figured I would keep it around to use as a Squid Proxy
Test box. I did not think that being on 11.04 could be the problem all
together!
I have other U 12.04.2 servers yet
Upgraded to ubuntu 14.04 and tried the bundled basic_ldap_auth binary, same
errors. Then recompiled Squid 3.3.10 tried that basic_ldap_auth binary, same
errors . . .
I guess I just am not meant to use Squid with AD . . . :-(
--
View this message in context:
Did you tried default squid?
apt-get install squid3
Maybe something else uses ldap port?
Try with (if I am not wrong):
debug_options 82,0 84,9
Do you have wireshark? Can you capture ldap requests on windows server from
Ubuntu?
Do you have firewall from Windows Server on?
From my practice it
On 21/11/2013 5:00 p.m., Brig wrote:
Upgraded to ubuntu 14.04 and tried the bundled basic_ldap_auth binary, same
errors. Then recompiled Squid 3.3.10 tried that basic_ldap_auth binary, same
errors . . .
I guess I just am not meant to use Squid with AD . . . :-(
Did you try the debug
Hi Brig,
Did you try something like this:
/usr/lib/squid3/basic_ldap_auth -P -R -u cn -b
cn=Users,dc=mydomain,dc=com -h ldap.mydomain.com
Please pay attention, that in practical way I defined that helper do not
provide support to such names:
john.doe
Better to use like this:
johndoe
Or
On Thu, Nov 14, 2013 at 11:12:15AM -0800, Brig wrote:
Hey Peter,
Thx for the reply!
I tried the command you suggested and I get error:
basic_ldap_auth: WARNING, could not bind to binddn 'Invalid credentials'
ERR Success
The same WARNING I'm able to simulate on my system when I put the
Hey Peter,
Thx for the reply!
I tried the command you suggested and I get error:
basic_ldap_auth: WARNING, could not bind to binddn 'Invalid credentials'
ERR Success
If I remove the -f sAMAccountName=%s part of the command you sent then I
get the error:
basic_ldap_auth.cc(739): pid=23194
17 matches
Mail list logo
