I created a multi-user application using Entity Framework, WebAPI, ASP.NET Identity. It basically reads the tenant's subdomain and uses it to read the connection string from the database and sets it at run time.
Everything is fine, a database is created, etc., but the only problem now is the ASP.NET identifier bearer.
When I created the access token for http: //tenant1.#####.com/token , it seems that the token is signed in one application (without the key machine), which allows you to access the controllers http: //tenant2.## ###. com , which should not be, as these are different subdomains / tenants.
Are there any ways around this? Or maybe I should look for a different security structure, not an ASP.NET identifier?
source share