我正在开发Mvc 5和新的Asp.net身份的多租户应用程序。 挑战在于两个用户可以拥有相同的用户名,而不是同一个租户。 我在大多数情况下已经弄明白了,但由于某种原因,Identity框架生成的所有表都有UserId列,但UserSecret实体的表除外。 是否有一个原因? 我想确保在用一个具有UserId列的实现替换它之前我没有遗漏一些东西。
I'm developing a multitenant application on Mvc 5 and the new Asp.net Identity. The challenge is that two users can have the same username, just not on the same tenant. I have this figured out for the most part, but for some reason all of the tables generated by the Identity framework have a UserId column, except the UserSecret entity's table. Is there a reason for this? I want to make sure I'm not missing something before I replace it with an implementation that has a UserId column.
最满意答案
默认实现是针对单租户应用程序设计的,它通过可扩展性(插入您自己的商店等)完成多租户应用程序支持。对于RTM,也不再有单独的UserSecret存储,因为已经滚动到用户自己(PasswordHash)。
The default implementation was designed for single tenant apps, it left multitenant app support to be done via the extensibility (plug in your own stores, etc) For RTM, there also is no longer a separate UserSecret store, as that has been rolled into the User itself (PasswordHash).
更多推荐
发布评论