I think this is impossible out of the box. When you check the db authassignment schema, you will see that it has a userid field that relates to your user table. If you have two different tables, you will need another unique identifier in the auth table. Do you absolutely need to have two different tables for your users? In fact, RBAC is very useful for sharing problems. Thus, you have one user table, but you can assign different roles to your users, such as "admin", "editor", etc. If you have two different user tables, what will you do if the user becomes an administrator? This is a difficulty that you do not have to cope with. If you absolutely need to, you will have to expand the RBAC functionality,so that you can refer to various tables.