CAS single sign-on system consolidation-Registration issues __cas

In recent time in the CAS single sign-on system, involving several subsystems of the integration problem. For registration, here's a choice:

Complete the registration within the subsystem, then synchronize the information to the CAS system, complete the registration of the basic information in the CAS system, such as username, mailbox, password, and then synchronize the basic information into the subsystem of the information needed

At the beginning, I was a bit entangled, and finally chose the way 2. The implementation process is as follows:

1 User access subsystem A, click "Register", the page jumps to the CAS system registration page;

2 The CAS registration page, fills in the user name, the mailbox, the password, completes registers, and automatically logs in;

3) the page jumps back to the a system page, at this time, a system can get the user has registered user name, password, mailbox, if a needs to use the user ID (such as a number, different from the user name) to do permissions management, then a can insert the user's information into their own user information table, and then according to need, Decide which values to store in the session, if a only need Username or mailbox, then save the user's basic information into his subsystem.

4 Then, the user by a page, access the Subsystem b page, with step 3, if B needs to do according to user ID Rights Management, then the basic information into the system table, otherwise only need to establish session can.