How the front end passes parameters across projects

there is a requirement in the work project. Project An and B are two projects respectively. The address of project An is www.aaa.com,B project address is www.bbb.com,. When you have logged in in project an and click a button to jump to project b, project b still maintains the login information of project a. The interfaces used by the two projects are the same, but the domain names are different, and the login information of the two projects needs to be interoperable. May I ask how to solve

Apr.09,2021

this can only be done by the backend for session persistence and interworking. If you need to jump seamlessly,

or through methods such as cookie, when the button is clicked, the authentication information is spliced to the url, and the bbb.com parses it and generates the cookie under the b project.
as for the specific certification process and means, it depends on the requirements of your project


https://www.cnblogs.com/ywlak.


you can consider being a login center, using tokens to handle login. After logging in under domain A, you can get a login token from the login center, jump to domain B and bring a token, and B uses a token to log in to the center to verify the login status.

you can take a look at single sign-on , which should solve your problem.


I don't know how your login is designed.
is the popular token now?

if only the front end saves information across pages
it is recommended to use localStorage

you should ask your backend more about this function

Menu