Articles in ensuring the design ideas, has omitted the original project name, project name and the database fields also used the alias instead. If similar accounts associated design requirements, reference Benpian design, implementation, their needs can be.
I. Background
NOTE: The following of private clients (personal business) and micro-channel public number is referred to the merger of private clients .
Background: There is a project for the private client, private client to carry out major personal and other services; embedded in other applications in the application of the system, such as corporate banking (corporate banking for the company understood the level of business ).
Some time ago, the demand side of the business there is a demand, to the private client and corporate client account to bind main function is:
1, the first time into account if the binding realize Bintang
2, tie public to the private account set
3, free for the public to the private account dence change
4, public to the private account unbind
Second, the system introduced
To expand the development of this modular design based on pre-existing base of business.
The existing system is as follows:
the public sign-on system (referred to as A)
to the private Login (authorization) system (referred to as B)
Customer Information Record System (C)
the need to develop a system or service:
to bind the public to the private system (referred to as D )
D system is mainly to provide public to the private accounts, provide binding, switching, unbundling, login time determination, provide external interface and other functions.
Design of the main service system access (abbreviated E)
E D systems primarily call system, binding association account, the account switching functions unbundling. Meanwhile, E is a systems project separate front and rear ends, related account just one module design, mainly related to the linked accounts linked accounts providing a binding and implemented as the front end.
Third, the design and implementation of programs:
First, the first to be determined according to their own business design database table, the system design is two tables, the main table and side tables, the main table is mainly used for front-end query, display information, the main job of the binding side tables, switching, unbind business processes, while side tables updated and timely information on the main table will also be updated.
1, the primary table mainly for display use: The main fields there are (table fields have letters instead of):
the private subscriber number: ZAID;
the public subscriber number: ZBId;
the public username: ZBName;
Operator ID: ZCId;
Operation member name: ZCName;
create and modify the underlying field is not listed here.
2, side tables in addition to the fields of the main table and also adds:
Role Number: FDId;
Role name: FDName;
customer number: FEId;
Customer Name: FEName;
logins record: FFNumber;
Last Login Time: FGTime;
create and modify the underlying field is not listed here.
Note: Due to the needs of show business sub-accounts and switching pages and pages show two different business information, so the design of the master schedule, in fact, if you just separate account switching system, the design table to the right.
Account switching Flowchart:
Account logout flow chart:
The implementation process:
1, the first micro-channel public number or configuration of the client to enter a link E system (link contains code user information, binding the login fields bind, source source), this request would be well-log E interception, interception after the transfer to the private system B will be in exchange for access to information for private users, and based on the public account is logged on to judge is to jump to the login page or jump to the main business system E home.
2, binding the user: If the user is logged by the login page, depending on whether the user is bound to prompt the user to bind a user clicks binding is binding, if the user chooses not binding, the whole in this login process is no longer playing the pop-up box prompts the user is bound to achieve is to make the user clicks recorded in the recording session, will determine whether the page jump to home users choose.
3, the user can operate the account in addition to the associated main business system, specifically to see their business is doing what function.
4, the switching account: If the user account switch, the switching process as handover account account flowchart shown in FIG. Switching accounts, mainly related to updated information exchange between multiple systems and you want to switch accounts.
We realize the idea here is that users choose to switch, we will first D system, select the query you want to switch accounts, and put under the individual user, the account is set to the last login. A account when asked to switch the system D, D system to the user returns to the last login account system A, A system to be switched to a holding account system exchange information of the user C and return the system to the E.
Of course, intermediate, and B relates to systems and access to private information checking the user, the process can be seen in detail illustrated.
5, the user unbundling, unbundling the user currently logged into unbound and non-users currently logged on, if the non-current user operation is performed to unbundle.
If the user is currently logged on, the first implementation of unbundling, and then out to perform logout security.
6, Logout Security: Security user performs logout operation, E B system system according to first to exchange a personal user code number, the code and the system returns to the A, A system performs logout operation system of its own, jump to login page.
Fourth, the problems encountered in debugging
1, according to first obtain different channels of different private user information, verification and access to information private to the user, without sometimes pass between fields or values in the delivery system, thus not obtaining the private user information, and then not get a bound account. Solution is to transfer between similar user or system code page, and if you can get timely detection code corresponding normal, then do not look at how to deliver in the past. Transfer between pages, it can be placed in sessionstorage.
2, whether it is binding on the login page Login or sign in, you need to get to the air control platform device fingerprint information before signing, so before jumping logon page requires loading, after obtaining a fingerprint device A pass system, A system the air supply control system. To get good debugging, loading and jump home page redirect problem device fingerprints.
V. Results and comments
Coordinated calls between systems, primarily to address security issues, such as the code of the private log acquired by the public system to the private system verification after a single failure, can ensure more secure access between systems.
After implementation and debugging, the system can achieve account binding, switching function unbundling.
If you have other questions, welcome to ask questions.
