CN117725568A

CN117725568A - Account management method and device, electronic equipment and storage medium

Info

Publication number: CN117725568A
Application number: CN202311864533.XA
Authority: CN
Inventors: 谢扬; 郑凌; 廖长江
Original assignee: Beijing Steam Memory Technology Co ltd
Current assignee: Beijing Steam Memory Technology Co ltd
Priority date: 2023-12-29
Filing date: 2023-12-29
Publication date: 2024-03-19

Abstract

The application discloses an account management method, an account management device, electronic equipment and a storage medium. The method specifically comprises the following steps: acquiring upstream account data of an upstream platform; creating an account entity in a preset identity conversion platform according to the upstream account data; synchronizing the account entity to at least one downstream platform, and respectively determining each downstream account data corresponding to each downstream platform; and determining an account association relationship according to the downstream account data and the account entity. According to the technical scheme of the embodiment of the application, according to the upstream account data which is already created by the upstream platform, an account entity is created in the identity conversion platform, the account entity is used as an intermediate medium to create accounts for a plurality of downstream platforms, and the downstream platforms are unified and associated, so that the account data of a user can be safely and stably synchronized to a plurality of other platforms or application programs, and the account entity is used as a medium and applied to a plurality of different platforms or application programs, the application range is greatly improved, and the flexibility of account management is further improved.

Description

Account management method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to an account management method, an apparatus, an electronic device, and a storage medium.

Background

With the rapid development of information technology, more and more service providers start to provide various information technology services for users, different requirements naturally correspond to different service systems, the number of various application systems and services is increasingly increased, and accordingly, enterprises or users have to manage more and more accounts and passwords in order to use the systems, which causes greater management risks.

Currently, for account management among different platforms or application programs, a lightweight directory access protocol is generally adopted by a person skilled in the relevant art to carry out overall planning, the protocol adopts a tree structure to store and manage data, but the mode cannot provide service for the platforms or application programs which do not support the protocol, so that the mode has poor flexibility for account management.

Disclosure of Invention

The application provides an account management method, an account management device, electronic equipment and a storage medium, so that the flexibility of account management is improved.

According to an aspect of the present application, there is provided an account management method, the method including:

acquiring upstream account data of an upstream platform;

creating an account entity in a preset identity conversion platform according to the upstream account data;

synchronizing the account entity to at least one downstream platform, and respectively determining each downstream account data corresponding to each downstream platform;

and determining an account association relationship according to the downstream account data and the account entity.

According to another aspect of the present application, there is provided an account management apparatus, the apparatus comprising:

the upstream data acquisition module is used for acquiring upstream account data of an upstream platform;

the account entity creation module is used for creating an account entity in a preset identity conversion platform according to the upstream account data;

the entity data synchronization module is used for synchronizing the account entity to at least one downstream platform and respectively determining downstream account data corresponding to each downstream platform;

and the association relation determining module is used for determining the association relation of the accounts according to the downstream account data and the account entity.

According to another aspect of the present application, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the account management method of any of the embodiments of the present application.

According to another aspect of the present application, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute the account management method according to any embodiment of the present application.

According to the technical scheme of the embodiment of the application, according to the upstream account data which is already created by the upstream platform, an account entity is created in the identity conversion platform, the account entity is used as an intermediate medium to create accounts for a plurality of downstream platforms, and the accounts are uniformly associated, so that the account data of a user can be safely and stably synchronized to a plurality of other platforms or application programs.

It should be understood that the description of this section is not intended to identify key or critical features of the embodiments of the application or to delineate the scope of the application. Other features of the present application will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of an account management method according to an embodiment of the present application;

FIG. 2 is a schematic diagram of account synchronization applicable in accordance with a second embodiment of the present application;

fig. 3 is a schematic structural diagram of an account management device according to a third embodiment of the present application;

fig. 4 is a schematic structural diagram of an electronic device implementing an account management method according to an embodiment of the present application.

Detailed Description

In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

Fig. 1 is a flowchart of an account management method according to an embodiment of the present application, where the method may be applied to the case of unified account management of multiple platforms or applications, and the method may be performed by an account management device, where the account management device may be implemented in hardware and/or software, and the account management device may be configured in an electronic device. As shown in fig. 1, the method includes:

s110, acquiring upstream account data of an upstream platform.

The upstream platform may be any platform system or application program requiring synchronization of the managed accounts, and accordingly, the upstream account data may be account information registered in the upstream platform by the user, for example, may be registered by a mailbox account number or a mobile phone number, so that the upstream account data may include information such as a mailbox account number and a mobile phone number besides the account number of the upstream platform.

S120, creating account entities in a preset identity conversion platform according to the upstream account data.

The identity conversion platform can be an application platform for storing and coordinating account synchronization among different platforms, for example, an Authing identity automation platform can be adopted. The account entity may be an account in an identity translation platform. It will be appreciated that in order to account synchronize upstream account data for multiple platforms or applications, the conversion and synchronization may be performed by an account entity in the identity conversion platform as an intermediary.

In an optional embodiment, the creating an account entity in the preset identity conversion platform according to the upstream account data may include: determining a mailbox prefix name of an upstream account according to the upstream account data; and creating an account entity according to the mailbox prefix name.

The upstream account data may include a mailbox account, where the mailbox prefix name includes a prefix and a suffix, and an account entity is created in the identity conversion platform by using the mailbox prefix name as a base, for example, the account of the account entity is created by using the mailbox prefix as a login name of an active directory of the account entity, so that the upstream account has a corresponding account in the identity conversion platform.

S130, synchronizing the account entity to at least one downstream platform, and respectively determining each downstream account data corresponding to each downstream platform.

The downstream platform may be each platform system or application program that the user desires to perform account synchronization, that is, other platform or application program that the accounts in the upstream platform can synchronize. It can be understood that each downstream platform can synchronize an account corresponding to an account of an upstream platform, so that a plurality of downstream platforms correspondingly construct a plurality of downstream accounts, and accordingly, the downstream account data can be account information included in the accounts of the downstream platforms.

In an optional embodiment, the synchronizing the account entity to at least one downstream platform, and determining each downstream account data corresponding to each downstream platform respectively may include: and synchronizing the account entity to each downstream platform according to a timing synchronization mechanism and an event triggering mechanism of the identity conversion platform so as to enable each downstream platform to respectively generate downstream account data corresponding to the mailbox prefix name.

The timing synchronization mechanism may be an intrinsic mechanism of the identity conversion platform and may be used to synchronize the orchestratable multi-platform data within a specified time or at specified time intervals. Similarly, the event triggering mechanism may also be an intrinsic mechanism of the identity transformation platform, and may be used to trigger a series of automatic processing procedures in the event of a preset condition or event. It should be noted that, under the control of the event triggering mechanism or the timing synchronization mechanism, the identity transformation platform may synchronize related data in the account entity to other platforms or applications (i.e., each downstream platform) that need to perform account synchronization. The downstream platform can register or generate the account of the downstream platform according to the mailbox prefix name of the upstream account data recorded by the account entity in the identity conversion platform, so that the mailbox prefix names of the downstream account data and the upstream account data can be corresponding.

In addition, the data in the account can also be converted between platforms or application programs when the account is synchronized. The process of synchronizing the identity conversion platform to each downstream platform may use a user data conversion node to synchronize data, for example, may include a field mapping, an expression mapping, a key-value (key-value), and the embodiment of the present application does not limit this.

S140, according to the downstream account data and the account entity, determining an account association relation.

The account association relationship may be used to characterize a correspondence (or mapping relationship) between the upstream account data and the downstream account data, where the account association relationship is represented on an association between the downstream account data and an account entity of the identity conversion platform. Based on the above steps, the determining the account association relationship according to the downstream account data and the account entity may include: feeding back and storing the data of each downstream account in an identity conversion platform; and according to the account entity, the downstream account data and the upstream account data are associated in the identity conversion platform, so that an account association relationship is obtained.

In the foregoing step, downstream account data is generated on each downstream platform, and the downstream platform feeds back the downstream account data to the identity conversion platform and establishes an association with the previously constructed account entity, where the account association relationship may be binding or mapping of the background by the ID (Identity document, identity number) of the account entity and the ID in the downstream account data. Because the account entity is constructed from the upstream account data, the account association information characterizes the association between the upstream merchant data and the respective downstream account data.

Example two

Fig. 2 is a schematic diagram of account synchronization applicable to embodiment two of the present application, which is some preferred embodiments provided on the basis of the foregoing embodiments. As shown in fig. 2, the specific steps are as follows:

the preferred embodiments of the present application are exemplified in practical applications such as account data from flybooks and account synchronization to platforms such as spike, LDAP (Lightweight Directory Access Protocol ) and Windows AD (Windows Active Directories, active directory). In this example, the flyer book is the upstream platform, and the data in the flyer book account corresponds to the upstream account data; similarly, the platform or application program such as the nail, the LDAP, the Windows AD and the like can be a downstream platform, and the corresponding account and data generated by the platform or the application program can be downstream account data.

As shown in fig. 2, the account data of the flyer user includes data such as user_id (user account), email (user mailbox), and customer_attrs (user attribute). By means of an identity automation platform Authing (corresponding to the identity conversion platform in the foregoing embodiment), an account entity defining a standard is established in Authing according to account data of the flyer user, and is used for storing all data of the user in the flyer (upstream platform), as shown in fig. 2, the account entity of the Authing user may include, but is not limited to, unique identification of the Authing system, user ids associated with various downstream platforms, email information, user phone numbers, user names usernames, remoids transferred from user attributes, password of the account, and the like.

The identity through Authing is automated and automatically synchronized to various downstream platforms such as nails, LDAP, windows AD, etc., by a timing synchronization mechanism and an event triggering mechanism. And after the user accounts are established by the downstream platforms, the association relation between the user ids of the accounts and the ids in the Authing is established. For example, when creating a Windows AD user, associating the returned objectGUID of the Windows AD to the windows_ad_user_id of the Authing; for another example, when a staple user is created, the userid returned by the staple is associated with the Authing dingtalk_user_id.

And then, converting the data of the user in the flyer book through an Authing user data conversion node so as to synchronize the user data of all downstream platforms. For example, a field mapping mode can be adopted to map from an original key to a new key; the method can adopt an expression mapping mode, adds expression support on the basis of field mapping, and can write simple expressions such as variables, ternary and the like for conversion. For example, mailbox prefixes may be extracted as usernames, demoids may be extracted from the customattrs nest data, random passwords may be generated, etc.; a fixed value assignment can be performed, and a fixed value is assigned to the field; fields may also be deleted, i.e. configured keys; enumeration values may also be mapped, the original enumeration value of the upstream platform may be mapped to a new enumeration value, and both keys and values may be mapped.

According to the method, the account data of the user in the upstream platform can be synchronized to the downstream platforms in different forms, even though development environments and running environments of various downstream platforms are different, the account entity in the identity conversion platform can be used as a bridge to synchronize and integrate the data of the upstream platform and the downstream platform, so that the flexibility and the efficiency of account management can be greatly improved, and the use experience of the user can be further improved.

Example III

Fig. 3 is a schematic structural diagram of an account management device according to a third embodiment of the present application. As shown in fig. 3, the apparatus 300 includes:

an upstream data obtaining module 310, configured to obtain upstream account data of an upstream platform;

an account entity creation module 320, configured to create an account entity in a preset identity conversion platform according to the upstream account data;

the entity data synchronization module 330 is configured to synchronize an account entity to at least one downstream platform, and determine each downstream account data corresponding to each downstream platform;

the association relationship determining module 340 is configured to determine an account association relationship according to the downstream account data and the account entity.

In an alternative embodiment, the account entity creation module 320 may include:

the prefix name determining unit is used for determining the mailbox prefix name of the upstream account according to the upstream account data;

and the entity creation unit is used for creating account entities according to the mailbox prefix names.

In an alternative embodiment, the entity data synchronization module 330 may be specifically configured to:

and synchronizing the account entity to each downstream platform according to a timing synchronization mechanism and an event triggering mechanism of the identity conversion platform so as to enable each downstream platform to respectively generate downstream account data corresponding to the mailbox prefix name.

In an alternative embodiment, the association determining module 340 may include:

the data feedback unit is used for feeding back and storing the data of each downstream account in the identity conversion platform;

and the account association unit is used for associating the downstream account data with the upstream account data in the identity conversion platform according to the account entity to obtain an account association relationship.

The account management device provided by the embodiment of the application can execute the account management method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of executing the account management methods.

Example IV

Fig. 4 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement embodiments of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.

As shown in fig. 4, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as account management methods.

In some embodiments, the account management method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. One or more of the steps of the account management method described above may be performed when the computer program is loaded into RAM 13 and executed by processor 11. Alternatively, in other embodiments, the processor 11 may be configured to perform the account management method in any other suitable way (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this application, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solutions of the present application are achieved, and the present application is not limited herein.

The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims

1. A method of account management, the method comprising:

acquiring upstream account data of an upstream platform;

2. The method of claim 1, wherein creating an account entity in a preset identity translation platform based on the upstream account data comprises:

determining a mailbox prefix name of the upstream account according to the upstream account data;

and creating the account entity according to the mailbox prefix name.

3. The method of claim 2, wherein synchronizing the account entity to at least one downstream platform, respectively determining each downstream account data corresponding to each downstream platform, comprises:

and synchronizing the account entity to each downstream platform according to a timing synchronization mechanism and an event triggering mechanism of the identity conversion platform so that each downstream platform respectively generates downstream account data corresponding to the mailbox prefix.

4. The method of claim 3, wherein the determining an account association from the downstream account data and the account entity comprises:

feeding back and storing the data of each downstream account in the identity conversion platform;

and according to the account entity, the downstream account data and the upstream account data are associated in the identity conversion platform, so that the account association relationship is obtained.

5. An account management apparatus, the apparatus comprising:

the entity data synchronization module is used for synchronizing the account entity to at least one downstream platform and respectively determining downstream account data corresponding to the downstream platforms;

and the association relation determining module is used for determining an account association relation according to the downstream account data and the account entity.

6. The apparatus of claim 5, wherein the account entity creation module comprises:

and the entity creation unit is used for creating the account entity according to the mailbox prefix name.

7. The apparatus of claim 6, wherein the entity data synchronization module is specifically configured to:

8. The apparatus of claim 7, wherein the association determination module comprises:

and the account association unit is used for associating the downstream account data with the upstream account data in the identity conversion platform according to the account entity to obtain the account association relation.

9. An electronic device, the electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the account management method of any one of claims 1-4.

10. A computer readable storage medium storing computer instructions for causing a processor to implement the account management method of any one of claims 1-4 when executed.