Missing configuration for the issuer of security tokens error
<p>I inherited an existing project without its development environment. I have UAT code and a backup of the Production database. I can run up the site locally via Visual Studio but have hit an authentication problem trying to setup a fresh standalone DEV server on AWS (single server, no load balancer). The doco indicates the Prod server is a dual server setup with a load balancer.</p>

<p>The front end site pages do display, although some search is not working. On trying to log into the backend pages, Chrome returns "The xxx page isn't working. xxx redirected you too many times." Using developer tools, I can see the page redirects back and forth between SWT?realm=... and sitefinity?wrap_defalted=true&amp;wrap_access_token... On the second redirect response header there is "X-Authentication-Error:Missing configuration for the issuer of security tokens '<a href="https://xxx/Sitefinity/Authenticate/SWT" rel="nofollow">https://xxx/Sitefinity/Authenticate/SWT</a>' "</p>

<p>I tried different values in the web.config lines:</p>

<pre><code>&lt;federatedAuthentication&gt;
        &lt;wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="http://localhost" requireHttps="true"/&gt;
        &lt;cookieHandler requireSsl="false"/&gt;
&lt;/federatedAuthentication&gt;
</code></pre>

<p>but that actually made things worse so I have reverted.</p>

<p>I checked all the settings mentioned in <a href="http://docs.sitefinity.com/administration-switch-to-claims-based-authentication" rel="nofollow">http://docs.sitefinity.com/administration-switch-to-claims-based-authentication</a> and they seem to be set correctly. I don't really know what else I can check to get this working.</p>

<p>I found <a href="http://docs.sitefinity.com/administration-configure-security" rel="nofollow">http://docs.sitefinity.com/administration-configure-security</a>, but it does not seem like these settings are set (I don't have access to Prod server so can't confirm if it is actually setup with load balancing). I am currently using a 30 day trial license so am not sure if this is contributing to the problem. The official license is in the process of being transferred by the client. The domain name associated with the official license would be different to the domain my new server is currently running on.</p>

<p>I am also running version 8 code on a version 9 install of Sitefinity. I wanted to get it working before I tried to upgrade the code. I think there was also an assembly load to manifest mismatch when I tried upgrading my local version.</p>