{"action":"opened","issue":{"url":"https://api.github.com/repos/MarimerLLC/csla/issues/675","repository_url":"https://api.github.com/repos/MarimerLLC/csla","labels_url":"https://api.github.com/repos/MarimerLLC/csla/issues/675/labels{/name}","comments_url":"https://api.github.com/repos/MarimerLLC/csla/issues/675/comments","events_url":"https://api.github.com/repos/MarimerLLC/csla/issues/675/events","html_url":"https://github.com/MarimerLLC/csla/issues/675","id":195944384,"number":675,"title":"Best way to handle Authorization Rules that behave differently on different pages?","user":{"login":"JustinBourlier","id":21001552,"avatar_url":"https://avatars.githubusercontent.com/u/21001552?v=3","gravatar_id":"","url":"https://api.github.com/users/JustinBourlier","html_url":"https://github.com/JustinBourlier","followers_url":"https://api.github.com/users/JustinBourlier/followers","following_url":"https://api.github.com/users/JustinBourlier/following{/other_user}","gists_url":"https://api.github.com/users/JustinBourlier/gists{/gist_id}","starred_url":"https://api.github.com/users/JustinBourlier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JustinBourlier/subscriptions","organizations_url":"https://api.github.com/users/JustinBourlier/orgs","repos_url":"https://api.github.com/users/JustinBourlier/repos","events_url":"https://api.github.com/users/JustinBourlier/events{/privacy}","received_events_url":"https://api.github.com/users/JustinBourlier/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-15T23:31:19Z","updated_at":"2016-12-15T23:31:19Z","closed_at":null,"body":"Before I start off, if there is a better forum to see examples / code, please point me to it.\r\n\r\nSo here's the problem I'm running into...  My authorization rules are basically need to be a bit different for my \"Admin\" role based on what page they are on.  I'm not sure the best way to do this, reading the HttpContext.Current page seems like an ugly way of doing things in the business layer.\r\n\r\nHere is my fictitious example:\r\nLet's say I have a list of \"CriminalCases\", where once an \"Officer\" selects a case to work, it becomes assigned to him/her.  In other words, they can Get/Edit the CriminalCase object on their \"WorkCases.aspx\"\r\n\r\nNow, I also have an \"Admin\" role.  Now this \"Admin\" is not allowed to edit any CriminalCase entities on this \"WorkCases.aspx\" page, however in the Admin area, they are able modify certain properties on this CriminalCase entity in the \"Admin\" page.    **What would be a clean way of handling such a scenario?**  Would love to find more built out example applications if there are any, I just see the following samples when I got the ebook \"Dependencies, EncapsulatedInvoke, EncapsulatedInvokeDto, ExceptionInspector, and FactoryImplementation, and Library.NET (Some sort of category / order project\"\r\n\r\n\r\n"}}
{"actor":{"display_login":"JustinBourlier"}}