{"action":"created","issue":{"url":"https://api.github.com/repos/aspnet/Security/issues/300","labels_url":"https://api.github.com/repos/aspnet/Security/issues/300/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Security/issues/300/comments","events_url":"https://api.github.com/repos/aspnet/Security/issues/300/events","html_url":"https://github.com/aspnet/Security/issues/300","id":90785173,"number":300,"title":"[AuthZ] Review authorize filter behavior again","user":{"login":"HaoK","id":6537861,"avatar_url":"https://avatars.githubusercontent.com/u/6537861?v=3","gravatar_id":"","url":"https://api.github.com/users/HaoK","html_url":"https://github.com/HaoK","followers_url":"https://api.github.com/users/HaoK/followers","following_url":"https://api.github.com/users/HaoK/following{/other_user}","gists_url":"https://api.github.com/users/HaoK/gists{/gist_id}","starred_url":"https://api.github.com/users/HaoK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HaoK/subscriptions","organizations_url":"https://api.github.com/users/HaoK/orgs","repos_url":"https://api.github.com/users/HaoK/repos","events_url":"https://api.github.com/users/HaoK/events{/privacy}","received_events_url":"https://api.github.com/users/HaoK/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-06-24T21:34:43Z","updated_at":"2015-06-24T22:29:11Z","closed_at":null,"body":"So with the new PR going in, there's no way for AuthorizeFilter to end up with a 403 unless it either asks for an scheme explicitly, or relies on an automatic one being populated (i.e. cookie).\r\n\r\nPerhaps this ok, but we should review just to be certain @blowdart "},"comment":{"url":"https://api.github.com/repos/aspnet/Security/issues/comments/115031223","html_url":"https://github.com/aspnet/Security/issues/300#issuecomment-115031223","issue_url":"https://api.github.com/repos/aspnet/Security/issues/300","id":115031223,"user":{"login":"HaoK","id":6537861,"avatar_url":"https://avatars.githubusercontent.com/u/6537861?v=3","gravatar_id":"","url":"https://api.github.com/users/HaoK","html_url":"https://github.com/HaoK","followers_url":"https://api.github.com/users/HaoK/followers","following_url":"https://api.github.com/users/HaoK/following{/other_user}","gists_url":"https://api.github.com/users/HaoK/gists{/gist_id}","starred_url":"https://api.github.com/users/HaoK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HaoK/subscriptions","organizations_url":"https://api.github.com/users/HaoK/orgs","repos_url":"https://api.github.com/users/HaoK/repos","events_url":"https://api.github.com/users/HaoK/events{/privacy}","received_events_url":"https://api.github.com/users/HaoK/received_events","type":"User","site_admin":false},"created_at":"2015-06-24T22:29:11Z","updated_at":"2015-06-24T22:29:11Z","body":"Basically if policy.ActiveAuthenticationScheme is not set, we rely on there being an automatic authentication setup to ever get a 403.  Its basically impossible for it to ever return a 403 otherwise"}}