Tieson Trowbridge

FWIW, I can confirm that Fluent Security 2.0 works with MVC4 and MVC5; I'm actively using it in a client app with no issues.

@kristofferahl Correct. Granted, I'm not doing anything fancy, so I can't speak to _everything_ working correctly, but authorization seems to function properly.

I solved the redirect problem by implementing a custom default policy handler, like so: ``` public class DenyAnonymousAccessPolicyViolationHandler : IPolicyViolationHandler { public ActionResult Handle(PolicyViolationException exception) { throw new HttpException(HttpContext.Current.User.Identity.IsAuthenticated ?...

You could do that, but then you always have to have an Accounts controller and a LogIn action - throwing the HttpException is relatively transparent and works with the MVC3...

Just out of curiosity, have you visited the project site at http://www.fluentsecurity.net/? To answer your question, yes, FluentSecurity (which I'll shorten to FS from now on) is primarily intended for...

I _think_ you could do that with a custom ISecurityPolicy implementation. Its API looks like ``` csharp PolicyResult Enforce(ISecurityContext context) ``` And you typically do something like ``` csharp public...

I do see this error in my ELMAH logs, but I haven't experienced an app crash while using a site with either the current release version, or the WebAPI WIP...

@kristofferahl Seems like the latter. I can zip up some relevant logs if you want. Appears to happen roughly once per day, so maybe it's a startup error?

@jrummell There is a set of unpublished packages that seemed to fix the duplicate key issue. It seems like they were generated using the [develop](https://github.com/kristofferahl/FluentSecurity/tree/develop) branch. I've attached the packages...

@jrummell No problem. I haven't used Fluent Security recently, but those were some packages @kristofferahl gave me to test when he was last actively working on this project. Not sure...