CN105787709A - Method of synchronizing multiple system accounts - Google Patents
Method of synchronizing multiple system accounts Download PDFInfo
- Publication number
- CN105787709A CN105787709A CN201610173285.8A CN201610173285A CN105787709A CN 105787709 A CN105787709 A CN 105787709A CN 201610173285 A CN201610173285 A CN 201610173285A CN 105787709 A CN105787709 A CN 105787709A
- Authority
- CN
- China
- Prior art keywords
- account
- data source
- white list
- user
- over
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention discloses a method of synchronizing multiple system accounts. The method comprises steps: an account management system acquires an identifier of a target application system, and the target application system is determined according to the identifier of the target application system; the account management system acquires first accounts in a main account data source corresponding to the target application system; the account management system incrementally stores the first accounts to a sub account data source corresponding to the target application system; the target application system acquires second accounts stored in the sub account data source; and the target application system searches a second account not stored in the main account data source in the second accounts, and the searched second account serves as a legacy account; and the target application system marks the searched legacy account as an abnormal account. By adopting the method of the invention, the unified degree of accounts between multiple systems under the user identity management system can be improved and the account reliability under the identity management system is improved.
Description
Technical field
The present invention relates to field of computer technology, particularly relate to a kind of multisystem account synchronous method, a kind of primary account number data source synchronizing method and device, seed account data source method of calibration and a device.
Background technology
Along with the raising of the development of computer technology and information level of the enterprise, KXG obtains increasing application in enterprises, and daily business is carried out and the daily management of enterprise also more and more uses information system.For using the enterprise of information system, it is everlasting day business just or management in many ways to carry out enterprise, can accumulate or use multiple application system, such as, on-the-job personnel's system, Email Accounts management system, attendance checking system etc., in order to employee's account of multiple for enterprise systems and authority being carried out the management of unified standard, improve the information security of each system of enterprise, facilitate manager that each account is carried out maintenance management, general enterprises can select to build unified identity management platform, and namely user identity management system is (English: IdentityManager；Write a Chinese character in simplified form: IDM).
To the enterprise using above-mentioned user identity management system, can use this system that multiple platforms of enterprise or the account of sub-application system are carried out unified management, be associated between account and enterprise staff or other related personnel in each sub-application system.
But, in existing IDM system, management to enterprise staff or the account of other related personnel such as client, outsourcing service provider, the establishment of such as account authority, access rights and deletion etc., it is all the maintenance by system or management personnel are performed manually by operation, whenever having New Hire Onboarding or old labor turnover, related personnel is required for establishment or the deletion of manually going to carry out account.Exactly because the maintenance and management of also manual account, it is easy to cause account deletion by mistake, lonely account, or cause privilege abuse etc..
It is to say, in existing user identity management system, can there is the phenomenon that the account of sub-application system can not be mated completely with the employee information in system in manual operation unavoidably, thus causing the reliability deficiency of the information system of enterprise.
Summary of the invention
Based on this, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, in a first aspect of the present invention, spy proposes a kind of multisystem account synchronous method.
A kind of multisystem account synchronous method, including:
Account management system obtains intended application system banner, determines described intended application system according to described intended application system banner；
Described account management system obtains the first account corresponding with described intended application system in primary account number data source；
Described first account increment is stored in the sub-account data source corresponding with described intended application system by described account management system；
Described intended application system obtains the second account of storage in described sub-account data source；
Described intended application system searches the second account being not stored in described primary account number data source as leaving over account in described second account；
The described account of leaving over found is labeled as abnormal account by described intended application system.
Optionally, described intended application system by described find leave over the step that account is labeled as abnormal account before also include: described intended application system obtains the account white list corresponding with described sub-account data source, leave over described in judgement whether account belongs to described account white list, if it is not, then perform described intended application system the described account of leaving over found is labeled as the step of abnormal account.
Optionally, also include after leaving over the step whether account belongs to described account white list described in described judgement: described leave over account be not belonging to described account white list time, described intended application system generates is left over, with telling, the white list interpolation prompting message that account is corresponding；Described intended application system receives the interpolation white list confirmation adding prompting message input for described white list, adds described account of leaving over to described account white list according to described interpolation white list confirmation.
Optionally, described primary account number data source includes at least one user；Described intended application system is searched the second account of being not stored in described primary account number data source in described second account and is also included as after the step leaving over account: described intended application system generates asks with described user-association corresponding to account of leaving over, receive the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding, obtains the association user corresponding with described ID；Described intended application system according to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
In addition, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, in a second aspect of the present invention, spy proposes a kind of primary account number data source synchronizing method.
A kind of primary account number data source synchronizing method, including:
Obtain intended application system banner, determine described intended application system according to described intended application system banner；
Obtain the first account corresponding with described intended application system in primary account number data source；
Described first account increment is stored in the sub-account data source corresponding with described intended application system.
Optionally, described method also includes: obtain the second account of storage in described sub-account data source；Described second account is searched the second account being not stored in described primary account number data source as leaving over account；When finding, described account of leaving over is labeled as abnormal account.
Optionally, described by described leave over the step that account is labeled as abnormal account before also include: obtain the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；If it is not, perform described described account of leaving over to be labeled as the step of abnormal account.
Optionally, also include after leaving over the step whether account belongs to described account white list described in described judgement: described leave over account be not belonging to described account white list time, generate and left over, with telling, the white list interpolation prompting message that account is corresponding；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, described primary account number data source includes at least one user；Described lookup in described second account is not stored in the second account in described primary account number data source and also includes as after the step leaving over account: generates and asks with described user-association corresponding to account of leaving over；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
Additionally, in a third aspect of the present invention, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, making existing identity management system there is the technical problem that reliability is not enough, spy proposes a kind of primary account number data source synchronizer.
Intended application system acquisition module, is used for obtaining intended application system banner, determines described intended application system according to described intended application system banner；
First account acquisition module, for obtaining the first account corresponding with described intended application system in primary account number data source；
Increment memory module, for storing described first account increment in the sub-account data source corresponding with described intended application system.
Optionally, described device also includes the second account acquisition module, leaves over account acquisition module and abnormal account mark module, wherein: described second account acquisition module is for obtaining the second account of storage in described sub-account data source；Described account acquisition module of leaving over for searching the second account being not stored in described primary account number data source as leaving over account in described second account；Described abnormal account mark module is for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
Optionally, described device also includes white list and determines module, for obtaining the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；Described leave over account be not belonging to described account white list time, call described abnormal account mark module.
Optionally, described white list determine module be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, described primary account number data source includes at least one user；Described device also includes user-association module, leaves over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
Additionally, in a fourth aspect of the present invention, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, making existing identity management system there is the technical problem that reliability is not enough, spy proposes a seed account data source method of calibration.
Obtain the second account of storage in sub-account data source；
Described second account is searched the second account being not stored in primary account number data source as leaving over account；
When finding, described account of leaving over is labeled as abnormal account.
Optionally, described by described leave over the step that account is labeled as abnormal account before also include: obtain the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；If it is not, perform described described account of leaving over to be labeled as the step of abnormal account.
Optionally, also include after leaving over the step whether account belongs to described account white list described in described judgement: described leave over account be not belonging to described account white list time, generate and left over, with telling, the white list interpolation prompting message that account is corresponding；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, described primary account number data source includes at least one user；Described lookup in described second account is not stored in the second account in primary account number data source and also includes as after the step leaving over account: generates and asks with described user-association corresponding to account of leaving over；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
In a fifth aspect of the present invention, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, making existing identity management system there is the technical problem that reliability is not enough, spy proposes a seed account data source calibration equipment.
Second account acquisition module, for obtaining the second account of storage in sub-account data source；
Leave over account acquisition module, for searching the second account being not stored in primary account number data source in described second account as leaving over account；
Abnormal account mark module, for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
Optionally, described device also includes white list and confirms module, for obtaining the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；If it is not, call described abnormal account mark module.
Optionally, described white list confirm module be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, described primary account number data source includes at least one user；Described device also includes user-association module, leaves over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
In a sixth aspect of the present invention, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, spy proposes a kind of multisystem account synchro system, including account management system and at least one application system, wherein: described account management system is for performing primary account number data source synchronizing method as described in respect of the second aspect of the invention；Described application system is for performing the sub-account data source method of calibration as described in fourth aspect present invention.
Implement the embodiment of the present invention, will have the advantages that
After have employed above-mentioned multisystem account synchronous method, primary account number data source synchronizing method and device and sub-account data source method of calibration and device, in process account being synchronized or verifying, the account not existed in sub-application system for existing in account management system is recovered；What then do not exist in account management system for existing in sub-application system leaves over account, it is marked as abnormal account, and carry out abnormal account process program further, so that account matching degree between account management system and sub-application system increases, increase the reliability of account in each system.Further, the lonely account in energy minimizing system or the situation of account abuse, the safety of the account management of raising user identity management system.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Wherein:
Fig. 1 is the schematic flow sheet of a kind of multisystem account synchronous method in an embodiment；
Fig. 2 is the structural representation of a kind of primary account number data source synchronizer in an embodiment；
Fig. 3 is the structural representation of a seed account data source calibration equipment in an embodiment.
Detailed description of the invention
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, it is clear that described embodiment is only a part of embodiment of the present invention, rather than whole embodiments.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art obtain under not making creative work premise, broadly fall into the scope of protection of the invention.
Based on this, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, making existing identity management system there is the technical problem that reliability is not enough, spy proposes a kind of account management mechanism based on multisystem.In the present embodiment, above-mentioned identity management system is made up of an account management system and several application systems, and the above-mentioned account management mechanism based on multisystem includes the primary account number data source synchronizing method based on account management system and the sub-account data source method of calibration based on sub-application system.The realization of said method all can be dependent on computer program, and this computer program can run on the computer system based on von Neumann system, and this computer program is account checking routine or the account synchronization program of user identity management system.Above computer system can be run server or the terminal of above computer program.
In the present embodiment, the sub-application system that user identity management system includes can have multiple, for instance the attendance checking system of enterprise staff, the payrool system of employee, employee Performance Evaluation System or enterprise mailbox management system etc..
Concrete, as it is shown in figure 1, Fig. 1 illustrates the schematic flow sheet of a kind of multisystem account synchronous method, comprise the steps:
Step S101: obtain intended application system banner, determine intended application system according to intended application system banner.
Intended application system is a sub-application system in identity management system, for instance can be enterprise mailbox management system.When some application system is carried out account comparison by needs, this application system is intended application system.In the present embodiment, the operation obtaining intended application system banner can be manually selected by user, can also be triggered according to timing mechanism by system, such as when having preset every 24 hours the account to enterprise mailbox management system carrying out an account comparison, system every 24 hours can shot timers, and trigger above-mentioned acquisition intended application system banner task.
In the present embodiment, each application system all carries corresponding application system mark, therefore when known target application system identifies, it is possible to determine the intended application system needing to carry out account comparison according to intended application system banner.
Step S102: obtain the first account corresponding with intended application system in primary account number data source.
Primary account number data source is the data source at all account places corresponding to account management system, and this data source can be the account data storage in the server of user account management system.User account management system is distributed account for other application systems and is stored in primary account number data source, so containing all account data that account relational system is the distribution of other application systems in primary account number data source.
Primary account number data source is searched all accounts corresponding with intended application system, in other words, searches all accounts of application system attribute item and intended application system matches, and obtain above-mentioned account as the first account.
Step S103: the first account increment is stored in the sub-account data source corresponding with intended application system.
Sub-account data source stores the account data in sub-application system, in all corresponding sub-account data source of a sub-application system.
But the process of above-mentioned increment storage is by the first account in storage primary account number data source is but not stored in the account in the sub-account data source corresponding with intended application system, newly-built above-mentioned account storing in the sub-account data source corresponding with intended application system, to eliminate the diversity of account in two account management systems and intended application system.In the present embodiment, it is necessary to compare for the first account corresponding with intended application system in primary account number data source, namely determine whether the first account corresponding with intended application system in primary account number data source is stored in intended application system.If there is the account being not stored in intended application system in the first account, then this account is carried out in intended application system account recovery.
Optionally, it is above-mentioned that by the first account increment, the detailed process stored in the sub-account data source corresponding with intended application system may is that each account in traversal the first account, the account traversed is searched in the sub-account data source corresponding with intended application system, if finding, then the next account of traversal；If not finding, then this account traversed newly-built in the sub-account data source corresponding with intended application system, until the traversal of the first account completes.
It should be noted that in the present embodiment, completing of step S101-step S103 can be completed by the server of account management system or primary account number data source place, and above-mentioned steps S101-step S103 namely primary account number data source synchronizing method.In other embodiments, the execution of above-mentioned steps S101-step S103 can also is that and performed by the computer equipment independent of account management system and sub-application system, this computer equipment can access primary account number data source and the sub-account data source corresponding with intended application system, and above-mentioned primary account number data source and sub-account data source can be operated, for instance account interpolation, account deletion etc..
After above-mentioned steps S101-step S103, all accounts in account management system and intended application system are absent from diversity, but also need to the legitimacy (namely whether existing in account management system) of each account of storage in intended application system is verified, concrete operating procedure following steps S104-step S106.
It should be noted that completing of step S104-step S106 can be completed by the server at the place, sub-account data source of intended application system or correspondence, and step S104-step S106 namely sub-account data source method of calibration.And, in other embodiments, the execution of above-mentioned steps S104-step S106 also can also is that the computer equipment independent of account management system and sub-application system performs, this computer equipment can access primary account number data source and the sub-account data source corresponding with intended application system, and above-mentioned primary account number data source and sub-account data source can be operated, for instance account interpolation, account deletion etc..
Step S104: obtain the second account of storage in sub-account data source.
Sub-account data source is the data source of the account storage corresponding with intended application system, contains all account information in intended application system.In this step, in the sub-account data source that reading is corresponding with intended application system, all accounts are as the second account.Second account is all accounts under intended application system.
Step S105: search the second account being not stored in primary account number data source in the second account as leaving over account.
All accounts in second account are traveled through, for each account traversed, primary account number data source is searched the account matched, if finding, then the next account of traversal；If not finding, then obtain this account for leaving over account.It is to say, all of account of leaving over is the unmatched account with the account of primary account number data source, it should these accounts are processed, for instance following steps S106 is labeled as abnormal account.
Step S106: the account of leaving over found is labeled as abnormal account.
After some account is labeled as abnormal account, generate corresponding abnormal account prompting, and generate corresponding prompting message and be sent to manager, manager these abnormal accounts are further processed, or can also directly delete all of abnormal account.
It should be noted that in the present embodiment, if there is some account, this account is stored in sub-account data source, but does not but store in primary account number data source, it is possible to for following several situations:
(1) this account is the special accounts such as test account, machine account, system account, it should continue to retain this account；
(2) employee that this account is corresponding has left office or has had other situations, it should deleted；
(3) this account is corresponding with certain user, it is not necessary to delete, it should continue to retain.
That is, not all account of leaving over is problematic account, has only to partial account number therein is processed in the process processed, for instance, account corresponding to situation (1) avoids the need for processing, and the account of situation (2) should be deleted.
In the present embodiment, will leave over before account is labeled as abnormal account, it is necessary to the concrete condition of account is judged, for instance, abnormal account need not be marked as during test account.
Such as, need whether account is that the special accounts such as test account judge, concrete: described by described find leave over the step that account is labeled as abnormal account before also include: obtain the account white list corresponding with described sub-account data source, leave over described in judgement whether account belongs to described account white list, if it is not, then perform described the described account of leaving over found to be labeled as the step of abnormal account.
In the present embodiment, system establishes an account white list, and the account comprised in this account white list can be not marked as abnormal account and not process.For leaving over account, before being labeled as abnormal account, it is judged that whether it belongs to account white list, is not if so, then labeled as abnormal account, if so, then perform above-mentioned steps S106.
Leave in the process whether account belongs to account white list in above-mentioned judgement, can also there is a kind of situation, although this account is not belonging to account white list, but this account should be added to account white list up, in such cases, in addition it is also necessary to provide channel this account to be added in account white list to system manager.
Concrete, in other embodiments, also include after leaving over the step whether account belongs to described account white list described in described judgement: described leave over account be not belonging to described account white list time, described generation is left over white list corresponding to account add prompting message with being told；Described reception adds the interpolation white list confirmation of prompting message input for described white list, adds described account of leaving over to described account white list according to described interpolation white list confirmation.
Find leave over account be not belonging to account white list time, generate corresponding white list according to this account information leaving over account and add prompting message, system manager can according to this white list add prompting message select this account is added in account white list, or select without.System manager is according to above-mentioned prompting message, the white list that adds adding prompting message input corresponding for above-mentioned white list confirms message and returns to the transmission equipment of prompting message, corresponding account of leaving over is added in account white list according to the white list confirmation of adding received by this equipment, it is to say, the account being added in account white list will not be marked as abnormal account again in the process that upper once account verifies.
It should be noted that in the present embodiment, it is understood that there may be many sub-application systems.Such as, for the identity management system of an enterprise staff, the attendance checking system of its correspondence, mailing system etc..In general, for employee " Zhang San ", it all has an account in each sub-application system.In the present embodiment, " Zhang San " is the user's name of a user, and the employee corresponding with " Zhang San " is exactly corresponding user, then corresponding many sub-accounts under this user, for instance: Email Accounts, work attendance account, wage account etc..
Above-mentioned find leave in account situation that may be present (3), this leaves over account with some user is corresponding, that is this account associates with certain user existed in account management system, but but but it is absent from primary account number data source, in such cases, it should add this account in primary account number data source and be managed with corresponding association user.
Concrete, in the method, primary account number data source includes at least one user；Described lookup in described second account is not stored in the second account in described primary account number data source and also includes as after the step leaving over account: generates and asks with described user-association corresponding to account of leaving over, receive the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding, obtains the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
After finding and leaving over account, account of leaving over according to finding generates corresponding user-association request, the request of this user-association can be used for being sent to system manager, then according to the concrete condition of this account, system manager selects that this is left over account and is associated with some user, namely incidence relation therebetween is set up, or select not carry out user-association, generate the user-association return information corresponding with user-association request according to the relevant information of system manager's input.
It should be noted that can also is that the account corresponding with user-association request according to user-association acquisition request and the historical data corresponding with the account, and generate the user-association return information corresponding with user-association request according to historical data.
In the present embodiment, user-association return information carries the ID needing association, after receiving user-association return information, obtain the ID comprised in this user-association return information, and according to user-association return information, primary account number data source is added this and leaves over account, and set up this leave over account with need the user that associates between incidence relation.
Optionally, in the present embodiment, above-mentioned multisystem account synchronous method, primary account number data source synchronizing method and sub-account data source method of calibration all can be configured so that timing performs, and, for different sub-application systems, different interval times can be set, because it is different during the security-critical degree of different sub-application systems, interval time for the high system account comparison of safe class could be arranged to the short period, interval time for the account comparison of insignificant sub-application system can arrange a relatively long interval time, thus under ensureing the premise of account number safety of identity management system, reduce the amount of calculation required for account comparison.
In addition, for solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, in the present embodiment, also proposed a kind of primary account number data source synchronizer, as in figure 2 it is shown, said apparatus includes:
Intended application system acquisition module 101, is used for obtaining intended application system banner, determines described intended application system according to described intended application system banner；
First account acquisition module 102, for obtaining the first account corresponding with described intended application system in primary account number data source；
Increment memory module 103, for storing described first account increment in the sub-account data source corresponding with described intended application system.
Optionally, in the present embodiment, as in figure 2 it is shown, said apparatus also includes the second account acquisition module 104, leaves over account acquisition module 105 and abnormal account mark module 106, wherein:
Described second account acquisition module 104 is for obtaining the second account of storage in described sub-account data source；
Described account acquisition module 105 of leaving over for searching the second account being not stored in described primary account number data source as leaving over account in described second account；
Described abnormal account mark module 106 is for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
Optionally, in the present embodiment, as in figure 2 it is shown, said apparatus also includes white list determines module 107, for obtaining the account white list corresponding with described sub-account data source；
Leave over described in judgement whether account belongs to described account white list；Described leave over account be not belonging to described account white list time, call described abnormal account mark module.
Optionally, in the present embodiment, described white list determine module 107 be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, in the present embodiment, described primary account number data source includes at least one user；As in figure 2 it is shown, described device also includes user-association module 108, leave over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
For solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, in the present embodiment, also proposed a seed account data source calibration equipment, as it is shown on figure 3, said apparatus includes:
Second account acquisition module 201, for obtaining the second account of storage in sub-account data source；
Leave over account acquisition module 202, for searching the second account being not stored in primary account number data source in described second account as leaving over account；
Abnormal account mark module 203, for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
Optionally, in the present embodiment, as it is shown on figure 3, said apparatus also includes white list confirms module 204, for obtaining the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；If it is not, call described abnormal account mark module.
Optionally, in the present embodiment, above-mentioned white list confirm module 204 be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
Optionally, in the present embodiment, above-mentioned primary account number data source includes at least one user；As it is shown on figure 3, described device also includes user-association module 205, leave over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
For solving conventional art cannot avoid the account of sub-application system can not mate completely with the relevant information in system because of labor management in identity management system, cause that the reliability of the information system of enterprise is not enough, existing identity management system is made to there is the technical problem that reliability is not enough, in the present embodiment, also proposed a kind of multisystem account synchro system, including account management system and at least one application system, wherein: described account management system is used for performing foregoing primary account number data source synchronizing method；Described application system is used for performing foregoing sub-account data source method of calibration.
Implement the embodiment of the present invention, will have the advantages that
After have employed above-mentioned multisystem account synchronous method, primary account number data source synchronizing method and device and sub-account data source method of calibration and device, in process account being synchronized or verifying, the account not existed in sub-application system for existing in account management system is recovered；What then do not exist in account management system for existing in sub-application system leaves over account, it is marked as abnormal account, and carry out abnormal account process program further, so that account matching degree between account management system and sub-application system increases, increase the reliability of account in each system.Further, the lonely account in energy minimizing system or the situation of account abuse, the safety of the account management of raising user identity management system.
Above disclosed it is only present pre-ferred embodiments, certainly can not limit the interest field of the present invention, the equivalent variations therefore made according to the claims in the present invention with this, still belong to the scope that the present invention contains.
Claims (23)
1. a multisystem account synchronous method, it is characterised in that including:
Account management system obtains intended application system banner, determines described intended application system according to described intended application system banner；
Described account management system obtains the first account corresponding with described intended application system in primary account number data source；
Described first account increment is stored in the sub-account data source corresponding with described intended application system by described account management system；
Described intended application system obtains the second account of storage in described sub-account data source；
Described intended application system searches the second account being not stored in described primary account number data source as leaving over account in described second account；
The described account of leaving over found is labeled as abnormal account by described intended application system.
2. multisystem account synchronous method according to claim 1, it is characterised in that described intended application system by described find leave over the step that account is labeled as abnormal account before also include:
Described intended application system obtains the account white list corresponding with described sub-account data source, leave over described in judgement whether account belongs to described account white list, if it is not, then perform described intended application system the described account of leaving over found is labeled as the step of abnormal account.
3. multisystem account synchronous method according to claim 1, it is characterised in that also include after leaving over the step whether account belongs to described account white list described in described judgement:
Described leave over account be not belonging to described account white list time, described intended application system generate with told leaves over account corresponding white list interpolation prompting message；
Described intended application system receives the interpolation white list confirmation adding prompting message input for described white list, adds described account of leaving over to described account white list according to described interpolation white list confirmation.
4. multisystem account synchronous method according to claim 1, it is characterised in that described primary account number data source includes at least one user；
Described intended application system is searched the second account of being not stored in described primary account number data source in described second account and is also included as after the step leaving over account:
Described intended application system generates leaves over, with described, the user-association request that account is corresponding, receive the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding, obtains the association user corresponding with described ID；
Described intended application system according to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
5. a primary account number data source synchronizing method, it is characterised in that including:
Obtain intended application system banner, determine described intended application system according to described intended application system banner；
Obtain the first account corresponding with described intended application system in primary account number data source；
Described first account increment is stored in the sub-account data source corresponding with described intended application system.
6. primary account number data source synchronizing method according to claim 5, it is characterised in that described method also includes:
Obtain the second account of storage in described sub-account data source；
Described second account is searched the second account being not stored in described primary account number data source as leaving over account；
When finding, described account of leaving over is labeled as abnormal account.
7. primary account number data source synchronizing method according to claim 6, it is characterised in that described by described leave over the step that account is labeled as abnormal account before also include:
Obtain the account white list corresponding with described sub-account data source；
Leave over described in judgement whether account belongs to described account white list；
If it is not, perform described described account of leaving over to be labeled as the step of abnormal account.
8. primary account number data source synchronizing method according to claim 7, it is characterised in that also include after leaving over the step whether account belongs to described account white list described in described judgement:
Described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；
Receive the interpolation white list confirmation adding prompting message input for described white list；
Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
9. primary account number data source synchronizing method according to claim 6, it is characterised in that described primary account number data source includes at least one user；
Described lookup in described second account is not stored in the second account in described primary account number data source and also includes as after the step leaving over account:
Generate and leave over, with described, the user-association request that account is corresponding；
Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；
Obtain the association user corresponding with described ID；
According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
10. a primary account number data source synchronizer, it is characterised in that including:
Intended application system acquisition module, is used for obtaining intended application system banner, determines described intended application system according to described intended application system banner；
First account acquisition module, for obtaining the first account corresponding with described intended application system in primary account number data source；
Increment memory module, for storing described first account increment in the sub-account data source corresponding with described intended application system.
11. primary account number data source synchronizer according to claim 9, it is characterised in that described device also includes the second account acquisition module, leaves over account acquisition module and abnormal account mark module, wherein:
Described second account acquisition module is for obtaining the second account of storage in described sub-account data source；
Described account acquisition module of leaving over for searching the second account being not stored in described primary account number data source as leaving over account in described second account；
Described abnormal account mark module is for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
12. primary account number data source synchronizer according to claim 11, it is characterised in that described device also includes white list and determines module, for obtaining the account white list corresponding with described sub-account data source；
Leave over described in judgement whether account belongs to described account white list；Described leave over account be not belonging to described account white list time, call described abnormal account mark module.
13. primary account number data source synchronizer according to claim 12, it is characterised in that described white list determine module be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
14. primary account number data source synchronizer according to claim 11, it is characterised in that described primary account number data source includes at least one user；
Described device also includes user-association module, leaves over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
15. a seed account data source method of calibration, it is characterised in that including:
Obtain the second account of storage in sub-account data source；
Described second account is searched the second account being not stored in primary account number data source as leaving over account；
When finding, described account of leaving over is labeled as abnormal account.
16. sub-account data source according to claim 15 method of calibration, it is characterised in that described by described leave over the step that account is labeled as abnormal account before also include:
Obtain the account white list corresponding with described sub-account data source；
Leave over described in judgement whether account belongs to described account white list；
If it is not, perform described described account of leaving over to be labeled as the step of abnormal account.
17. sub-account data source according to claim 16 method of calibration, it is characterised in that also include after leaving over the step whether account belongs to described account white list described in described judgement:
Described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；
Receive the interpolation white list confirmation adding prompting message input for described white list；
Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
18. sub-account data source according to claim 15 method of calibration, it is characterised in that described primary account number data source includes at least one user；
Described lookup in described second account is not stored in the second account in primary account number data source and also includes as after the step leaving over account:
Generate and leave over, with described, the user-association request that account is corresponding；
Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；
Obtain the association user corresponding with described ID；
According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
19. a seed account data source calibration equipment, it is characterised in that including:
Second account acquisition module, for obtaining the second account of storage in sub-account data source；
Leave over account acquisition module, for searching the second account being not stored in primary account number data source in described second account as leaving over account；
Abnormal account mark module, for when leaving over account described in finding, being labeled as abnormal account by described account of leaving over.
20. sub-account data source according to claim 19 calibration equipment, it is characterised in that described device also includes white list and confirms module, for obtaining the account white list corresponding with described sub-account data source；Leave over described in judgement whether account belongs to described account white list；If it is not, call described abnormal account mark module.
21. sub-account data source according to claim 20 calibration equipment, it is characterised in that described white list confirm module be additionally operable to described leave over account be not belonging to described account white list time, generate with told leave over account corresponding white list interpolation prompting message；Receive the interpolation white list confirmation adding prompting message input for described white list；Described account of leaving over is added to described account white list according to described interpolation white list confirmation.
22. sub-account data source according to claim 19 calibration equipment, it is characterised in that described primary account number data source includes at least one user；
Described device also includes user-association module, leaves over, with described, the user-association request that account is corresponding for generating；Receiving the user-association return information corresponding with the request of described user-association, described user-association return information carries leaves over, with described, the ID that account is corresponding；Obtain the association user corresponding with described ID；According to described user-association return information, in described primary account number data source add described in leave over account, described in leave over account with described associate user corresponding.
23. a multisystem account synchro system, including account management system and at least one application system, wherein:
Described account management system for perform as arbitrary in claim 5 to 9 as described in primary account number data source synchronizing method；
Described application system for perform as arbitrary in claim 15 to 18 as described in sub-account data source method of calibration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610173285.8A CN105787709A (en) | 2016-03-24 | 2016-03-24 | Method of synchronizing multiple system accounts |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610173285.8A CN105787709A (en) | 2016-03-24 | 2016-03-24 | Method of synchronizing multiple system accounts |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105787709A true CN105787709A (en) | 2016-07-20 |
Family
ID=56391843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610173285.8A Pending CN105787709A (en) | 2016-03-24 | 2016-03-24 | Method of synchronizing multiple system accounts |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105787709A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332928A (en) * | 2017-07-31 | 2017-11-07 | 广东欧珀移动通信有限公司 | Using account synchronization management method, device, storage medium and electronic equipment |
| CN108830470A (en) * | 2018-06-01 | 2018-11-16 | 北京金山数字娱乐科技有限公司 | A kind of method and device of account processing |
| CN109005140A (en) * | 2017-06-06 | 2018-12-14 | 陈鑫尧 | A kind of method of safe account registering and logging |
| CN109062489A (en) * | 2018-07-19 | 2018-12-21 | 腾讯科技（深圳）有限公司 | Message treatment method, device, storage medium and electronic device |
| CN110019508A (en) * | 2017-09-28 | 2019-07-16 | 北京国双科技有限公司 | A kind of method of data synchronization, apparatus and system |
| CN111311267A (en) * | 2020-03-05 | 2020-06-19 | 支付宝(杭州)信息技术有限公司 | Multi-account risk prevention and control method, system and equipment |
| CN111445210A (en) * | 2020-03-27 | 2020-07-24 | 咪咕文化科技有限公司 | Account cleaning method and device, electronic equipment and storage medium |
| CN112069137A (en) * | 2020-09-02 | 2020-12-11 | 北京百度网讯科技有限公司 | Method and device for generating information, electronic equipment and computer readable storage medium |
| CN112667742A (en) * | 2020-09-24 | 2021-04-16 | 紫光云技术有限公司 | Master-slave copy account synchronization optimization method |
| WO2021120586A1 (en) * | 2019-12-17 | 2021-06-24 | 聚好看科技股份有限公司 | Account synchronization method, mobile device and smart television |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101072103A (en) * | 2007-03-09 | 2007-11-14 | 腾讯科技（深圳）有限公司 | Method and system for multi-account log-in instant communication software |
| CN101719880A (en) * | 2009-11-13 | 2010-06-02 | 东南大学 | Fusion system for multi-protocol multi-account instant messages and working method thereof |
| CN103268233A (en) * | 2013-06-05 | 2013-08-28 | 四目信息科技（上海）有限公司 | Method for combining account number of platform system and account number of third party system in computer system |
| CN105376263A (en) * | 2015-12-24 | 2016-03-02 | 青岛洪锦电子商务有限公司 | Unified management method for multi-system data |
-
2016
- 2016-03-24 CN CN201610173285.8A patent/CN105787709A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101072103A (en) * | 2007-03-09 | 2007-11-14 | 腾讯科技（深圳）有限公司 | Method and system for multi-account log-in instant communication software |
| CN101719880A (en) * | 2009-11-13 | 2010-06-02 | 东南大学 | Fusion system for multi-protocol multi-account instant messages and working method thereof |
| CN103268233A (en) * | 2013-06-05 | 2013-08-28 | 四目信息科技（上海）有限公司 | Method for combining account number of platform system and account number of third party system in computer system |
| CN105376263A (en) * | 2015-12-24 | 2016-03-02 | 青岛洪锦电子商务有限公司 | Unified management method for multi-system data |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109005140A (en) * | 2017-06-06 | 2018-12-14 | 陈鑫尧 | A kind of method of safe account registering and logging |
| CN107332928A (en) * | 2017-07-31 | 2017-11-07 | 广东欧珀移动通信有限公司 | Using account synchronization management method, device, storage medium and electronic equipment |
| CN110019508A (en) * | 2017-09-28 | 2019-07-16 | 北京国双科技有限公司 | A kind of method of data synchronization, apparatus and system |
| CN108830470A (en) * | 2018-06-01 | 2018-11-16 | 北京金山数字娱乐科技有限公司 | A kind of method and device of account processing |
| CN109062489A (en) * | 2018-07-19 | 2018-12-21 | 腾讯科技（深圳）有限公司 | Message treatment method, device, storage medium and electronic device |
| WO2021120586A1 (en) * | 2019-12-17 | 2021-06-24 | 聚好看科技股份有限公司 | Account synchronization method, mobile device and smart television |
| CN111311267A (en) * | 2020-03-05 | 2020-06-19 | 支付宝(杭州)信息技术有限公司 | Multi-account risk prevention and control method, system and equipment |
| CN111311267B (en) * | 2020-03-05 | 2022-06-21 | 支付宝(杭州)信息技术有限公司 | Multi-account risk prevention and control method, system and equipment |
| CN111445210A (en) * | 2020-03-27 | 2020-07-24 | 咪咕文化科技有限公司 | Account cleaning method and device, electronic equipment and storage medium |
| CN111445210B (en) * | 2020-03-27 | 2023-10-20 | 咪咕文化科技有限公司 | Account cleaning method and device, electronic equipment and storage medium |
| CN112069137A (en) * | 2020-09-02 | 2020-12-11 | 北京百度网讯科技有限公司 | Method and device for generating information, electronic equipment and computer readable storage medium |
| CN112069137B (en) * | 2020-09-02 | 2024-05-17 | 阿波罗智联(北京)科技有限公司 | Method, device, electronic equipment and computer readable storage medium for generating information |
| CN112667742A (en) * | 2020-09-24 | 2021-04-16 | 紫光云技术有限公司 | Master-slave copy account synchronization optimization method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105787709A (en) | Method of synchronizing multiple system accounts | |
| US10579803B1 (en) | System and method for management of application vulnerabilities | |
| CN105722081B (en) | Intelligent equipment networking method and device | |
| CN109471865A (en) | A kind of off-line data management method, system, server and storage medium | |
| CN104486346A (en) | Stepping stone system | |
| CN110808839B (en) | Processing method, device, equipment and medium for block chain abnormal data | |
| CN110188103A (en) | Data account checking method, device, equipment and storage medium | |
| CN107729576A (en) | The management method and system of archives | |
| CN107369234B (en) | Unlocking method and system | |
| CN110245145A (en) | Structure synchronization method and apparatus of the relevant database to Hadoop database | |
| JP5000359B2 (en) | Information management system and information management method | |
| CN108614882A (en) | A kind of file management method and system based on server | |
| CN114386896A (en) | Information sending method, page display device, electronic equipment and medium | |
| CN110232279A (en) | A kind of leak detection method and device | |
| CN110795763A (en) | Electronic certificate processing method, query method, device, equipment, platform and medium | |
| CN107316176A (en) | The control method and device of declaration form processing | |
| CN102281291A (en) | Log-in method and system | |
| CN109947592A (en) | A kind of method of data synchronization, device and relevant device | |
| US20150140957A1 (en) | Prepaid phone card charging | |
| CN108024090A (en) | A kind of abnormal localization method and device for video monitoring platform | |
| CN110874790A (en) | Certificate association management method and device | |
| CN109711816A (en) | Cooperative institution's approaches to IM, device, computer equipment and storage medium | |
| KR20120124931A (en) | User-definable Process-based Management System for Urban Planning and Recording Media for the Same | |
| CN112395476A (en) | Engineering data management method | |
| CN106888195A (en) | Verification method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160720 |