On 18/03/11 02:05, Bleiker Gregory wrote:
Hi Amos
Thank you for your answer. You really mean 3.2? 3.1 seems the latest I can grab. Do you know of a 3.2. Windows binary?
Ah. No Sorry. Usable Squid-3 on Windows pretty much ends at the 3.0
experimental bundle Acme provide.
We have hit a few big problems building later releases. Some people have
managed to get 3.1 to build after some hacks, but even then report
mystery problems running it.
If anyone is keen to assist tracking down these build issues I'm very
happy to pass over a todo list. We are concentrating on MinGW builds at
present. (Hint: Cygwin requires that someone to donate machine access to
the project build farm).
Amos
-----Ursprüngliche Nachricht-----
Von: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx]
Gesendet: Mittwoch, 16. März 2011 12:14
An: squid-users@xxxxxxxxxxxxxxx
Betreff: Re: Fixed Auth for cache_peer for anonymous ssrs
On 16/03/11 21:36, Bleiker Gregory wrote:
Hi
I'm trying to set up squid so I can use it with MS Reporting Server
(SSRS). The ssrs site has ms windows authentication (NTLM) enabled, as
some reports need to be protected. Some however are "public". For these
it is still required to log in. I would like to configure squid in such
a way that if you call the ssrs site over squid (with the squid port
number in the url) then it should always use some fixed credentials for
the backend which I would specify in the squid.conf.
I have tried to do this with
cache_peer myssrs.mydomain.local parent 80 3120 no-query originserver
name=3DmyAccel login=3Dmyuser@mydomain:mypassword
but the user is still always asked to give his credentials.
Is it possible to configure squid so that no username is asked and that
the backend is always presented some fixed credentials?
Not for NTLM. Squid can only sends Basic auth credentials to peers.
The 3.2 beta releases can do Negotiate/Kerberos to peers which may be
supported by that system.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.11
Beta testers wanted for 3.2.0.5
