ClearOS Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001362ClearOSapp-web-proxy - Web Proxypublic2013-10-05 10:362014-06-25 12:25
Assigned Touser2 
PlatformOSOS Version
Product Version6.4.0 
Target Version6.6.0 Beta 2Fixed in Version6.6.0 Beta 2 
Summary0001362: User authentication makes some services which are incapable of authentication fail. Requires whitelist.
DescriptionWhen user authentication is enabled, some sites will fail due to the fact that they are incapable of using the underlying authentication. For this reason, there should be a whitelist function of the proxy server.

Even when whitelisted in the default policy of the content filter, these sites will fail because they don't have intrinsic rights to use the proxy.

Again, this is only needed when authentication is present because the regular content filter controls are sufficient.
Steps To ReproduceSet up a server with user authentication. Content filter is optional.

Use dropbox.

You will see requests fail with a TCP_DENIED. Even though it may be on the siteexceptionlist.

Additional InformationBy adding a new 'whitelist' category, you can modify which sites do NOT require authentication. This would be added to squid.conf.

acl whitelist dstdomain

# Whitelist: Do not require authentication
http_access allow whitelist
http_access allow CONNECT SSL_ports whitelist
TagsNo tags attached.
Attached Files

- Relationships
has duplicate 0001664closeduser2 Some web applications do not have a configurable option to authenticate. This causes problems in the proxy. 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2013-10-05 10:36 dloper New Issue
2013-10-07 09:21 user2 Status new => confirmed
2014-04-22 13:34 user2 Target Version 6.5.0 Updates => 6.6.0 Beta 1
2014-04-30 04:50 user2 Target Version 6.6.0 Beta 1 => 6.6.0 Beta 2
2014-06-04 11:56 user2 Relationship added has duplicate 0001664
2014-06-04 11:56 user2 Status confirmed => resolved
2014-06-04 11:56 user2 Fixed in Version => 6.6.0 Beta 2
2014-06-04 11:56 user2 Resolution open => fixed
2014-06-04 11:56 user2 Assigned To => user2
2014-06-25 12:25 user2 Status resolved => closed