Build a third-party login platform

There are already two e-commerce websites, one information website, and three internal systems. Each system has its own user table.
1. Now I want to create a unified login point to provide login function. How should I design the login form? How should the users of the login form be related to users of other systems? I want to achieve a unique identity for e-commerce users and information users. Users also have their own unique identifier.
2. Each logged-in user has his own role. For example, the e-commerce role has permissions to manage orders, open new stores, etc. How to design the permissions?
3. How to do third-party login?

Reply content:

There are already two e-commerce websites, one information website, and three internal systems. Each system has its own user table.
1. Now I want to create a unified login point to provide login function. How should I design the login form? How should the users of the login form be related to users of other systems? I want to achieve a unique identity for users in the e-commerce category and information category. Users also have their own unique identifier.
2. Each logged-in user has his own role. For example, the e-commerce role has permissions to manage orders, open new stores, etc. How to design the permissions?
3. How to do third-party login?

Permission issues are solved by each system itself. Just search for how to design it. You can also refer to the ACL design of mature frameworks.

The certification center requires at least:
1- When logging in to the certification center, users can choose their own login account type, such as e-commerce, information, and internal. After logging in, they can bind accounts in other systems.
2- E-commerce, information, and internal systems must provide authentication APIs for the authentication center
3- The authentication center needs to allow users to merge their own associated account information
4- Third-party authentication provides token authentication and APIs for reading basic user information

I can’t answer you in detail. I can only handle more content at my own discretion based on needs and existing system conditions.

Two methods:
1. Create single sign-on (SSO) yourself, provide a unified login interface, and pay attention to the domain name of cookies.
2. Use the ready-made OAuth solution, that is, third-party login, which is relatively mature and easy to use.

Supplement: I see that you are using Laravel. Laravel should have an SSO extension package. If it were me, I would define these second-level domain names directly in the routing, so there is no need for SSO. Laravel has an OAuth-Server extension. Bag.

I think your question is about php, I suggest you check out these information
https://github.com/bshaffer/o...
http://bshaffer.github.io/oau...