How to design the system single sign-on architecture

Multi-domain, multiple subsystems want to authenticate user information through a unified portal. Ask you at present single-point login basic process, large-scale website is how to practice and user information encryption verification of several standards.

Reply content:

Multi-domain, multiple subsystems want to authenticate user information through a unified portal. Ask you at present single-point login basic process, large-scale website is how to practice and user information encryption verification of several standards.

Unified login portals, such as login.xxx.com, embed a js,login.xxx.com/login.js.php on each page, determine whether to log in, process logins, and so on. If you have logged in, set a JS variable, the content is login.xxx.com SessionID, and then the JS variable back to the site backstage, such as www.a.com, background read this SessionID related content can determine whether to log in. can use Memcache,redis and so on to achieve the Kua server access session

