title: LightSwitch 2013 HTML authentication without authorization
body: <p>I am trying to do something that I think should be very simple, but LightSwitch 2013 HTML is making it seemingly very hard.</p>
  
  <p>I want to have a LightSwitch HTML client and web service that require Windows authentication.  Any user is fine.  I don't want to do any authorization beyond "yes, they authenticated."</p>
  
  <p>When I enable Windows authentication in my LightSwitch properties, even for "any user," like so:</p>
  
  <p><img src="https://i.stack.imgur.com/l62Lm.png" alt="Authentication settings"></p>
  
  <p>it seems that LightSwitch still wants to do authorization, so it wants the <code>_IntrinsicData</code> connection string set and pointing at a valid ASP.NET membership database.  I've tried doing the following:</p>
  
  <ol>
  <li>Setting authentication to none in LightSwitch and just having IIS do it - this causes repeated prompts and eventually a 401 in the client.</li>
  <li>Changing the role provider configuration to use Windows instead of SQL as you normally would in straight ASP.NET - this causes the same repeated 401 in the client.</li>
  <li>Various levels of code-based permissions as described at <a href="http://msdn.microsoft.com/en-us/library/vstudio/ff851957.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/vstudio/ff851957.aspx</a> - this causes repeated 401 or doesn't seem to do anything depending on where I set it.</li>
  <li>Completely removing or disabling the role provider from <code>web.config</code> - this causes LightSwitch to complain at the next create/update that the Role Manager is disabled.</li>
  <li>Messing with <code>deny</code> and <code>allow</code> entries in <code>web.config</code> and authentication set to Windows while the app properties are set to anonymous; that leads to 401.</li>
  </ol>
  
  <p>If I leave the settings as shown and do nothing special, then when a create/update operation is submitted, LightSwitch tries to talk to the non-existent membership database and times out eventually.</p>
  
  <p>How do I get authentication with blanket authorization without having to carry around a membership database?</p>