Home > other >  API interface development if only the interface need RBAC authorization management, background don&#
API interface development if only the interface need RBAC authorization management, background don&#

Time:11-11

Wei Xi teach you - Yii2 RESTful API developing speaks 6 and 7, the API user and background management of user authentication and authorization, all user information table is in the same table,
Question 1: how to put a table into two tables, API users and administrators want to split into two tables, API user list, a list administrators, how to implement the
Question 2: how to realize respectively, the API interface to the user, and the background administrator user authentication and access management without interfering with each other, don't want to be in the same table
Two problems seem to be the same idea

CodePudding user response:

1, this why the two tables? You give users to assign different permissions to control user access behavior; Or to the user group, different groups have different permissions,
2, each method can be configured access, each user can have different permissions,

CodePudding user response:

Some form of business, only need to define each role permissions, API identification, is enough, and the background does not need to have administrator role can allocate good

CodePudding user response:

All files, like from point A to point B, can produce 100 ways, how to walk, completely the be fond of,
Understand the principle, understand his point A to point B no matter how many nodes by he end up as A into A, everything is vain, o m drag Buddha,

CodePudding user response:

Come on, you can think how make all

CodePudding user response:

Need to verify permissions interface directly to a field judgment under no

CodePudding user response:

The same problem,