title: asp.net core identity and identityserver
body: <p>I'm following <a href="http://docs.identityserver.io/en/release/quickstarts/6_aspnet_identity.html" rel="nofollow noreferrer">this walkthrough</a> on integrating asp.net core identity with IdentityServer but have hit a few roadblocks.</p>
  
  <p>Where I'm updating the ConfigureServices method, if I follow the guide and use</p>
  
  <pre><code>services.AddIdentity&lt;IdentityUser, IdentityRole&gt;()
          .AddEntityFrameworkStores&lt;ApplicationDbContext&gt;()
          .AddDefaultTokenProviders();
  </code></pre>
  
  <p>I can no longer access any of the account related functions. The routing for the register link changes from</p>
  
  <pre><code>~/Identity/Account/Register
  </code></pre>
  
  <p>to</p>
  
  <pre><code>~/?area=Identity&amp;page=%2FAccount%2FRegister
  </code></pre>
  
  <p>Which breaks all account related functions</p>
  
  <p>If I leave it at</p>
  
  <pre><code>services.AddDefaultIdentity&lt;IdentityUser&gt;()
                  .AddEntityFrameworkStores&lt;ApplicationDbContext&gt;()
                  .AddDefaultTokenProviders();
  </code></pre>
  
  <p>Then the routing still works, I can enter my credentials via the login page and the login is successful, but</p>
  
  <pre><code>SignInManager.IsSignedIn(User)
  </code></pre>
  
  <p>returns false, so I'm guessing something is fundamentally broken here.</p>
  
  <p>I have added identityserver to my ConfigureServices:</p>
  
  <pre><code>    services.AddIdentityServer()
                      .AddDeveloperSigningCredential()
                      .AddInMemoryPersistedGrants()
  .AddInMemoryIdentityResources(Config.IdentityResources.GetIdentityResources())
                      .AddInMemoryApiResources(Config.APIResources.GetApiResources())
                      .AddInMemoryClients(Config.Clients.GetClients())
                      .AddAspNetIdentity&lt;IdentityUser&gt;();
  </code></pre>
  
  <p>Any ideas what needs to change - I'm guessing its something in the latest version of asp.net core that has caused this has it?</p>