Search squid archive

Re: OWA accelerator authentication weirdness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alan Lehman wrote:
The order in which our auth_param lines are configured can alter the
first authentication method tried. You will need to look at the
debugging trace in cache.log to see which is generating which question

Amos

Only basic is enabled:
auth_param basic children 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours

Do I need to select a program for basic?

found in cache.log:
2009/01/08 14:38:19.713| CacheManager::registerAction: registering legacy basicauthenticator
2009/01/08 14:38:19.713| CacheManager::findAction: looking for action basicauthenticator
2009/01/08 14:38:19.713| CacheManager::registerAction: registered basicauthenticator
2009/01/08 14:41:22.010| CacheManager::registerAction: registering legacy basicauthenticator
2009/01/08 14:41:22.010| CacheManager::registerAction: registered basicauthenticator

The OWA web server has both basic and "Windows Integrated Authentication" enabled. If I disable "windows integrated", OWA works fine, but I need activesync also, which does not work without "windows integrated" enabled.

Thanks,
Alan

Um, further on my other email.
Try some of the settings to disable pass-thru on the specific ports and/or peer:

http://wiki.squid-cache.org/Features/ConnPin


Amos
--
Please be using
  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE11
  Current Beta Squid 3.1.0.3

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux