title: Integrated Security with Impersonate=true / Connection String issue / ASP.NET
body: <p>We have a website deployed with Impersonate=true.</p>
  
  <p>A connection string is defined as this:</p>
  
  <blockquote>
    <p>Integrated Security=SSPI;Persist Security Info=false;Initial
    Catalog=MyDatabase;Data Source=MyServer;</p>
  </blockquote>
  
  <p>I assume Persist Security Info is redundant as that only applies to SQL authentication? We need to use integrated security as can't have passwords in the config file due to corporate security policies.</p>
  
  <p>The website runs under a service account. The service account has permissions to access the database, but other accounts do not have access (security policy).</p>
  
  <p>The problem we're facing is the user account is being passed to the database and being rejected, due to Impersonate=true.</p>
  
  <p>We're required to have Impersonate=true for a Single Sign-On component to work.</p>
  
  <p>Is this a catch 22 or is there a solution?</p>
  
  <p>I hope I've written this clearly enough!</p>