Normal a universal access platform account details field is fixed, but when combined with various business, found a lot of business account details of the system is not completely the same, some systems need to these fields, other and other fields, excuse me, how to solve this problem, and in the future in the new system can continue to use this access platform? (after the new system is also likely to need a new account details)

CodePudding user response:

Must first to the unified account business system, there are a source of a unified, unified synchronization of the account system of every system of account data, unified account system in only the most basic information, such as account id, account name, password, etc., as for other information by each business system according to their own need to supplement,

CodePudding user response:

refer to the original poster crazy_sniper response:

normal a universal access platform account details field is fixed, but when combined with various business, found a lot of business account details of the system is not completely the same, some systems need to these fields, and other and other fields, could you tell me how to solve this problem, and in the future in the new system can continue to use this access platform? (after the new system is also likely to need a new account details)

This is not a single point of landing, single sign-on understanding once,

CodePudding user response:

Account to allow differentiation properties of nature, when they should be allowed to design, usually center need only common attributes, the other in their respective systems