What are you doing in your HttpApplication's AuthenticateRequest event?
On Tue, Sep 9, 2008 at 8:22 PM, jsmorris <[EMAIL PROTECTED]> wrote:
>
> @Jimmy I am setting the PrincipalPermission on each of my actions in
> the controller and the PrincipalPermission is working as advertised.
> I do not have a restriction to access the URL in my web.config. If I
> comment out all my manual exceptions, things work. And, if I change
> the role to "Foo" and since I don't have the Foo role, that is when I
> get the ASP.NET error page.
>
> My complete action is
>
> [PrincipalPermission(SecurityAction.Demand, Role =
> Roles.Administrator)]
> public void Index()
> {
> // throw new Exception("This is a test of an Exception");
> // throw new ControllerException("This is a test of a
> controller exception");
> throw new SecurityException("This is a test of a security
> exception");
>
> PropertyBag["feeds"] = Feed.FindAll();
> }
>
> @Patrick I am working off a nightly build 92?, so I am pretty
> current. As I stated to Jimmy, I am setting my PrincipalPermission at
> the action level, so the thread you referenced doesn't seem
> applicable. Unless I am misunderstanding your suggestions, I believe
> my problem is with how monorail catches exceptions and then figures
> out which rescue view to use and when it doesn't find it in bubbles
> the exception out to ASP.NET.
>
> If I throw the ControllerException or just a plain Exception, the
> rescues work, so what is stumping me is why is the SecurityException
> any different since it is throw in the same place as the others.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
