<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>aC forum: Clients attempting to access restricted functions see 403 errors</title>
  <link>http://www.activecollab.com/forums/topic/2309/</link>
  <description>Recent posts on topic: Clients attempting to access restricted functions see 403 errors</description>
  <dc:language>en-us</dc:language>
  <pubDate>Mon, 08 Sep 2008 07:56:33 UTC</pubDate>
  
  <item>
    <link>http://www.activecollab.com/forums/post/10962/#post10962</link>
    <guid>http://www.activecollab.com/forums/post/10962/#post10962</guid>
    <title>Post #2 by Ilija Studen</title>
    <dc:creator>Ilija Studen</dc:creator>
    <description><![CDATA[<p>Hi Brandon,<br />
<br />
What are the cases when clients are provided with a link to a page or tool they don't have access or permission to use? Basically, pages and tools should never appear to users who can't use them.<br />
<br />
We'll see to improve error messages and provide more useful tools when displaying than, but I still don't have any details on how and when it will be done.</p>]]></description>
    <pubDate>Thu, 29 Nov 2007 07:17:27 UTC</pubDate>
  </item>
  <item>
    <link>http://www.activecollab.com/forums/post/10960/#post10960</link>
    <guid>http://www.activecollab.com/forums/post/10960/#post10960</guid>
    <title>Post #1 by cbtrussell</title>
    <dc:creator>cbtrussell</dc:creator>
    <description><![CDATA[<p>aC allows client users to be restricted from accessing certain areas of the site. So far so good.<br />
<br />
Issue #1 - Users without access to a functional area should not see that menu item in the nav bar. (If user can't view/add/manage tickets, the tickets tab should not be visible).<br />
<br />
Issue #2 - IMPORTANT - When a client user attempts to access a function they don't have permission to use, they are given a nasty 403 error. That is a deal breaker for us and so far, the only real glaring defect we've found in the application that prevents us from inviting customers to use the tool.<br />
<br />
Ilijah - are these issues you're planning to address in an upcoming release? I was honestly surprised to find the 403 error because it's the only example of a glaring defect in an otherwise polished initial release.<br />
<br />
Looking forward to your comments!<br />
<br />
Thanks,<br />
<br />
Brandon</p>]]></description>
    <pubDate>Thu, 29 Nov 2007 06:01:04 UTC</pubDate>
  </item>
</channel>
</rss>