search for: authorizedusers

...ntlm_auth --helper-protocol=squid-2.5-basic auth_param basic children 5 auth_param basic realm Squid proxy-caching web server auth_param basic credentialsttl 2 hours And my ACL's acl all src 0.0.0.0/0.0.0.0 acl localhost src 127.0.0.1/255.255.255.255 http_access allow localhost acl AuthorizedUsers proxy_auth REQUIRED http_access allow all AuthorizedUsers http_access deny all http_reply_access allow all And if I try to browse anywebsite at all, the squid access.log shows TCP_DENIED/407 In the squid cache.log I can see it authenticateValidateUser: Validating Auth_user request '0...

...0 auth_param ntlm max_challenge_lifetime 2 minutes auth_param basic program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of=MERCURY\WebAccess auth_param basic children 5 auth_param basic realm Squid proxy-caching web server auth_param basic credentialsttl 2 hours acl AuthorizedUsers proxy_auth REQUIRED http_access allow all AuthorizedUsers -- Michael St. Laurent Hartwell Corporation

My question is how have people implemented different types of users in their Web applications using user-engine? As for my application, I use single table inheritance in order to derive several different types of users, such as "moderators," "editors," etc ... For example, let''s say that I want to create a moderator. I define a new moderator class and Controller like

...S # Example rule allowing access from your local networks. Adapt # to list your (internal) IP networks from where browsing should # be allowed #acl our_networks src 192.168.1.0/24 192.168.2.0/24 #http_access allow our_networks ##acl my_network src 175.10.0.0/16 ##http_access allow my_network acl AuthorizedUsers proxy_auth REQUIRED http_access allow all AuthorizedUsers ##acl password proxy_auth REQUIRED ##http_access allow password # And finally deny all other access to this proxy http_access deny all . . . This spawns another question - why do I need an auth_param for both ntlm and basic authentication...

...S # Example rule allowing access from your local networks. Adapt # to list your (internal) IP networks from where browsing should # be allowed #acl our_networks src 192.168.1.0/24 192.168.2.0/24 #http_access allow our_networks ##acl my_network src 175.10.0.0/16 ##http_access allow my_network acl AuthorizedUsers proxy_auth REQUIRED http_access allow all AuthorizedUsers ##acl password proxy_auth REQUIRED ##http_access allow password # And finally deny all other access to this proxy http_access deny all . . . This spawns another question - why do I need an auth_param for both ntlm and basic authentication...

[Cross Posted in Rails Engines] I''m taking a new approach to how I view user data, I think in the end it will be faster for the system anyways... What I''m doing is using LoginEngine/UserEngine combo on my site for authorization, and I want each user to have a profile that they edit and maintain. Each user would have 1 profile. My question is getting my profile and my user

...) because MSIE is broken and always selects the > first advertised authentication scheme even if the standard clearly says it should select > the strongest authentication scheme. Now search for: TAG: http_access Find "INSERT YOUR OWN RULE(S) HERE" and put in this acl entry acl AuthorizedUsers proxy_auth REQUIRED http_access allow all AuthorizedUsers Comment out any acls providing access to anyone in the local network. The above ACL forces people to authenticate. Be sure this section ends with a line that looks like this: http_access deny all Save your edits. Change group ownersh...