How to Prevent permission session conflicts caused by the same user name in different backgrounds with the same second-level domain names

For example, the addresses of the two websites are teacher.aaa.comfather.aaa.com. The names of the users in the two backend are peter's rbac permissions saved using sessions. How can we achieve simultaneous logon to sessions and permissions for both websites in a browser? no conflict. For example, the addresses of the two websites are
Teacher.aaa.com
Father.aaa.com

The names of users on both backend are peter.
Rbac permission used
Saved By session
How can we ensure that both a browser and a website can log on to the session at the same time without conflict of permissions?

Reply content:

For example, the addresses of the two websites are
Teacher.aaa.com
Father.aaa.com

The names of users on both backend are peter.
Rbac permission used
Saved By session
How can we ensure that both a browser and a website can log on to the session at the same time without conflict of permissions?

Set these two websitesSessionOfCookie domainYou can set the scope to the corresponding website (including the second-level domain name ),SessionIt will not conflict with each other.

Set the Domain entry of the cookie

Sessions will not be the same for different domains, so they will not conflict.
The account's permissions are controlled by the program rather than the session. The session only helps you determine who the account is ".