I THINK this scenario is not supported by ASP.NET Identity as it needs a DbContext which extends IdentityDbContext (or similar).
Why are you forcing Identity into your DB-First context?
You can use a Code-First context for Identity alongside your other DB-First context without problems...