title: What are the alternatives to Windows security subsystem in .NET winforms applications
body: <p>I'm about to start development work on .NET 4.0 winforms application running on top of a Microsoft SQL Server 2012 database.</p>
  
  <p>The number of users supposed to use the application might be any where between 2 to 10 and the application should be able to run either on a single stand alone computer or in an intranet in a windows environment. </p>
  
  <p>in case the application is run on a single computer, each user would log into the application (not into windows) and perform what ever tasks they are authorized to do and then log out of the application. </p>
  
  <p>If the application is configured to run on a small intranet, each user would log into the application from there respective office computers and do what ever they are authorized to do.</p>
  
  <p>So, the application can run on a single none networked machine, where a single windows login account is being shared by staff at the facility but i have a requirement to allow access to certain application functionality depending on who is logged into the application, NOT who is logged into windows as the account might just be shared.</p>
  
  <p>I have previously deployed ASP.NET applications in networked environments and used the SQL Membership, Roles and Profiles provider for authentication and authorization While for winforms apps, i have relied on active directory authentication.</p>
  
  <p>Now with this particular project, i am wondering what the best solution might be. Probably some one here has implemented a solution for such a scenario and can give advice.</p>
  
  <p>I have looked at this <a href="http://www.codeproject.com/Articles/27670/Implementing-Application-Security-with-Client-Appl" rel="nofollow">http://www.codeproject.com/Articles/27670/Implementing-Application-Security-with-Client-Appl</a> solution but i still want to hear from the SO masses.</p>
  
  <p>ALSO, any recommendation for a better post Title is welcome.</p>