We have a link on normal content that points to pdf dokument on a folder that is only available to Registered users. If an unregistered user clicks the link he/she get's this:

_________________________

Exception Details: System.UnauthorizedAccessException: You are not authorized to access /Global/PDS/EU_product_data_sheets/

ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via , the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.

___________________________

So what we want to do, is just Like Matti said in the first message: Open up a register form for our unregistered users instead of this error message. Problem is we can't catch the error and thus can't redirect unauthorized users to register form? Is there anyway how we could achieve our goal?

Bump.

Anyone found a solution to this?

I have faced many similar situations where one wants to list files (or pages in menus e.g) where the listings are public, but the actual file (or page) requires a logged in user. Of course we would like to make use of the ACL, but how avoid such System.UnauthorizedAccessException at first? Basically one would like to have something similar to "list but not read"-access. 

There must be some common way to deal with this? (not using ACL and checking access directly in code everywhere is not very nice..)

Any solution to this? Would like to redirect the user to the login page instead of showing a Server Error...

My solution to the problem was to create a common base page (inheriting EPiServer.TemplatePage) from which all my aspx-pages dervies. In this base page I override the GetPage(PageReference pageLink, ILanguageSelector selector) method.

In this method I manually fetch the Page object via DataFactory.Instance.GetPage(pageLink), that is, with out any restrictions. Then I fetch the required access for the page and compares that to the currently logged-in (or even unauthenticated) user and takes action depending on what roles are missing.

Not sure if this really is the best implementation, but it does the job for me. I can send you some more details if you want.