title: ClaimsPrincipalPermission and unit testing
body: <p>I like using the ClaimsPrincipalPermission in my code, but there is a problem: The authorization code is interfering with unit tests.</p>
  
  <p>How would you solve this problem? Off the top of my head I can think of three solutions:</p>
  
  <ul>
  <li>Have a separate configuration section for testing purposes that loads an authentication manager that always returns true to all CheckAccess calls</li>
  <li>Add a code snippet to the real authentication manager that always returns true to all CheckAccess calls when a unit test is running</li>
  <li>Create a custom authorization attribute that doesn't invoke authentication manager when in a unit test</li>
  </ul>
  
  <p>Any other suggestions for a solution? If you implemented one of the above mentioned solutions I would love to see what you did.</p>