Component login method, client login authorization method, device and electronic equipment

Abstract

The embodiment of the invention discloses a component login method, a client login authorization method, a client login authorization device and electronic equipment. A specific embodiment of the method comprises the following steps: sending a component configuration request to an associated service component; in response to a received client login identification code corresponding to the component configuration request sent by the service component, sending a login authorization request to the service component through the remote calling interface, the login authorization request carrying the client login identification code and user information; and in response to a received component interface transport protocol service link corresponding to the login authorization request sent by the service component, skipping to a component service page pointed by the component interface transport protocol service link. This embodiment relates to a component such that a client can access the component in a lightweight manner.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a component login method, a client login authorization method, a device, and an electronic device. Background Art

[0002] Currently, SaaS services have become a widely used service delivery method on the Internet. SaaS stands for Software-as-a-Service, which means "software as a service". It means providing services to the outside world through complete and mature software. Related service delivery models include IaaS (Infrastructure-as-a-Service) and PaaS (Platform-as-a-Service). SaaS services can be embedded in other Internet products in the form of components. They have a high degree of freedom and can be combined and removed at will, which facilitates the rapid access of some general functions and improves production efficiency. At present, the client logs in to the service component in the usual way: using CAS (Central Authentication Service) to complete cross-domain login.

[0003] However, the above method usually has the following technical problems: using the central authorization service for cross-domain login requires the client and the component to simultaneously access the central authorization service center, and requires the client and the component to simultaneously maintain the central authorization service center, making client access to the component cumbersome.

[0004] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Summary of the invention

[0005] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0006] Some embodiments of the present disclosure propose a component login method, a client login authorization method, an apparatus, an electronic device, a computer-readable medium, and a program product to solve one or more of the technical problems mentioned in the above background technology section.

[0007] In the first aspect, some embodiments of the present disclosure provide a component login method, which includes: sending a component configuration request to an associated service component; in response to receiving a client login identification code corresponding to the component configuration request sent by the above service component, sending a login authorization request to the above service component through a remote call interface, wherein the above login authorization request carries the above client login identification code and user information; in response to receiving a component interface transmission protocol service link corresponding to the above login authorization request sent by the above service component, jumping to the component service page pointed to by the above component interface transmission protocol service link.

[0008] In a second aspect, some embodiments of the present disclosure provide a client login authorization method, the method comprising: in response to receiving a login authorization request sent by a client, parsing the client login identification code and user information contained in the above login authorization request; reading the client configuration information corresponding to the above client login identification code; in response to reading the client configuration information corresponding to the above client login identification code, verifying the above user information; in response to the above user information verification being passed, generating a component interface transfer protocol service link based on the above user information, and sending the above component interface transfer protocol service link to the above client.

[0009] Optionally, the component interface transfer protocol service link carries encrypted user information; and the method further includes: in response to detecting an access operation of the client to access the component interface transfer protocol service link, decrypting the encrypted user information contained in the component interface transfer protocol service link to obtain decrypted user information; writing a login state corresponding to the decrypted user information; in response to successful writing of the login state, pushing a component service page to the client.

[0010] Optionally, the above-mentioned generating a component interface transfer protocol service link based on the above-mentioned user information includes: encrypting the above-mentioned user information according to a preset symmetric key to generate encrypted user information; generating an initial component interface transfer protocol service link according to the above-mentioned encrypted user information; encrypting the above-mentioned symmetric key to generate an encrypted symmetric key; adding the above-mentioned encrypted symmetric key and the associated component domain name to the above-mentioned initial component interface transfer protocol service link to obtain the component interface transfer protocol service link.

[0011] Optionally, before the above-mentioned response to receiving a login authorization request sent by the service component and parsing out the client login identification code and user information contained in the login authorization request sent by the above-mentioned service component, the above-mentioned method also includes: in response to receiving a component configuration request sent by the above-mentioned client, generating client configuration information corresponding to the above-mentioned client according to the above-mentioned component configuration request; in response to the completion of the configuration of the above-mentioned client configuration information, generating a client login identification code corresponding to the above-mentioned client.

[0012] In the third aspect, some embodiments of the present disclosure provide a component login device, the device comprising: a first sending unit, configured to send a component configuration request to an associated service component; a second sending unit, configured to respond to receiving a client login identification code corresponding to the component configuration request sent by the service component, and send a login authorization request to the service component through a remote call interface, wherein the login authorization request carries the client login identification code and user information; a jumping unit, configured to respond to receiving a component interface transmission protocol service link corresponding to the login authorization request sent by the service component, and jump to the component service page pointed to by the component interface transmission protocol service link.

[0013] In a fourth aspect, some embodiments of the present disclosure provide a client login authorization device, the device comprising: a parsing unit, configured to, in response to receiving a login authorization request sent by a client, parse out the client login identification code and user information contained in the above login authorization request; a reading unit, configured to read the client configuration information corresponding to the above client login identification code; a verification unit, configured to, in response to reading the client configuration information corresponding to the above client login identification code, verify the above user information; a generation unit, configured to, in response to the above user information being verified, generate a component interface transfer protocol service link according to the above user information, and send the above component interface transfer protocol service link to the client corresponding to the login authorization request sent by the above service component.

[0014] Optionally, the component interface transmission protocol service link carries encrypted user information.

[0015] Optionally, the client login authorization device also includes: a decryption unit, configured to, in response to detecting an access operation of the client accessing the component interface transmission protocol service link, decrypt the encrypted user information contained in the component interface transmission protocol service link to obtain decrypted user information; a writing unit, configured to: write a login state corresponding to the decrypted user information; and a pushing unit, configured to push a component service page to the client in response to successful writing of the login state.

[0016] Optionally, the generation unit is further configured to: encrypt the above-mentioned user information according to a preset symmetric key to generate encrypted user information; generate an initial component interface transfer protocol service link according to the above-mentioned encrypted user information; encrypt the above-mentioned symmetric key to generate an encrypted symmetric key; add the above-mentioned encrypted symmetric key and the associated component domain name to the above-mentioned initial component interface transfer protocol service link to obtain the component interface transfer protocol service link.

[0017] Optionally, before the parsing unit, the client login authorization device also includes: an information generation unit, configured to generate client configuration information corresponding to the above-mentioned client in response to receiving a component configuration request sent by the above-mentioned client according to the above-mentioned component configuration request; an identification code generation unit, configured to generate a client login identification code corresponding to the above-mentioned client in response to the completion of the configuration of the above-mentioned client configuration information.

[0018] In a fifth aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation of the first or second aspect above.

[0019] In a sixth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation of the first aspect or the second aspect is implemented.

[0020] In a seventh aspect, some embodiments of the present disclosure provide a computer program product, including a computer program, which, when executed by a processor, implements the method described in any implementation of the first aspect or the second aspect.

[0021] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the component login method of some embodiments of the present disclosure, it is not necessary for the client and the component to access the central authorization service center at the same time, so that the client can access the component in a lightweight manner. Specifically, the reason why the client accesses the component is cumbersome is that the cross-domain login using the central authorization service requires the client and the component to access the central authorization service center at the same time, and the client and the component need to maintain the central authorization service center at the same time. Based on this, the component login method of some embodiments of the present disclosure first sends a component configuration request to the associated service component. Thus, the configuration of the client can be completed on the component side. Then, in response to receiving the client login identification code corresponding to the component configuration request sent by the above service component, a login authorization request is sent to the above service component through a remote call interface. Among them, the above login authorization request carries the above client login identification code and user information. Thus, an authorization request can be sent directly to the component through a remote call interface without accessing the central authorization service center. Finally, in response to receiving the component interface transmission protocol service link corresponding to the above login authorization request sent by the above service component, jump to the component service page pointed to by the above component interface transmission protocol service link. Therefore, it is possible to communicate directly with the component through the remote call interface, so that the client and the component do not need to access the central authorization service center at the same time, so that the client can access the component in a lightweight manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0023] Figure 1 is an information timing interaction diagram between a component login method and a client login authorization method in some embodiments of the present disclosure;

[0024] Figure 2 is a flow chart of some embodiments of the component login method according to the present disclosure;

[0025] Figure 3 is a flow chart of some embodiments of the client login authorization method according to the present disclosure;

[0026] Figure 4 is a schematic diagram of the structure of some embodiments of the component login device according to the present disclosure;

[0027] Figure 5 It is a structural schematic diagram of some embodiments of the client login authorization device according to the present disclosure;

[0028] Figure 6It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0030] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0031] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0032] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0033] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0034] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0035] Figure 1 It is an information timing interaction diagram between the component login method and the client login authorization method of some embodiments of the present disclosure.

[0036] exist Figure 1 In the embodiment, first, the client 101 can send a component configuration request 103 to the associated service component 102. After that, after receiving the configuration request 103, the service component 102 sends a client login identification code 104 to the client 101. Next, after receiving the client login identification code 104, the client 101 sends a login authorization request 105 to the service component 102. Then, after receiving the login authorization request 105, the service component 102 sends a component interface transfer protocol service link 106 to the client 101. Finally, the client 101 can access the component service page 107 through the component interface transfer protocol service link 106.

[0037] Continue to refer Figure 2 , shows a process 200 of some embodiments of the component login method according to the present disclosure. The component login method comprises the following steps:

[0038] Step 201: Send a component configuration request to an associated service component.

[0039] In some embodiments, the execution body of the component login method (eg Figure 1 The client 101 shown in the figure can send a component configuration request to the associated service component. Here, the associated service component can refer to a component that provides Internet application services. For example, the associated service component can be a SaaS component. The component configuration request can refer to a request for personalized configuration of the client. For example, the component configuration request can be a request for configuration of the main color of the page, customization of sensitive copy, etc.

[0040] Step 202, in response to receiving the client login identification code corresponding to the component configuration request sent by the service component, sending a login authorization request to the service component through a remote call interface.

[0041] In some embodiments, the above-mentioned execution subject may send a login authorization request to the above-mentioned service component through a remote call interface in response to receiving a client login identification code corresponding to the above-mentioned component configuration request sent by the above-mentioned service component. The above-mentioned login authorization request carries the above-mentioned client login identification code and user information. The client login identification code may be an identification code generated by the service component that uniquely identifies the client. The user information may be the account information of the user who logs in to the client. For example, the user information may include: user name, account number. The remote call interface may refer to a pre-set access interface of the service component. For example, the remote call interface may be an RPC (Remote Procedure Call) interface. That is, the above-mentioned execution subject may send a login authorization request to the above-mentioned service component by calling the remote call interface.

[0042] Step 203, in response to receiving the component interface transmission protocol service link corresponding to the login authorization request sent by the service component, jump to the component service page pointed to by the component interface transmission protocol service link.

[0043] In some embodiments, the above-mentioned execution subject may jump to the component service page pointed to by the above-mentioned component interface transfer protocol service link in response to receiving the component interface transfer protocol service link corresponding to the above-mentioned login authorization request sent by the above-mentioned service component. The component interface transfer protocol service link may refer to a link to access the service page provided by the service component. For example, the component interface transfer protocol service link may be an HTTP (Hyper Text Transfer Protocol) link. The component service page may be a page that provides SaaS component services. For example, the component service page may be a separate web page, an iFrame window, or an H5 page. That is, the above-mentioned execution subject may jump to the component service page by accessing the above-mentioned component interface transfer protocol service link.

[0044] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the component login method of some embodiments of the present disclosure, it is not necessary for the client and the component to access the central authorization service center at the same time, so that the client can access the component in a lightweight manner. Specifically, the reason why the client accesses the component is cumbersome is that the cross-domain login using the central authorization service requires the client and the component to access the central authorization service center at the same time, and the client and the component need to maintain the central authorization service center at the same time. Based on this, the component login method of some embodiments of the present disclosure first sends a component configuration request to the associated service component. Thus, the configuration of the client can be completed on the component side. Then, in response to receiving the client login identification code corresponding to the component configuration request sent by the above service component, a login authorization request is sent to the above service component through a remote call interface. Among them, the above login authorization request carries the above client login identification code and user information. Thus, an authorization request can be sent directly to the component through a remote call interface without accessing the central authorization service center. Finally, in response to receiving the component interface transmission protocol service link corresponding to the above login authorization request sent by the above service component, jump to the component service page pointed to by the above component interface transmission protocol service link. Therefore, it is possible to communicate directly with the component through the remote call interface, so that the client and the component do not need to access the central authorization service center at the same time, so that the client can access the component in a lightweight manner.

[0045] Further references Figure 3 , showing some embodiments of the client login authorization method according to the present disclosure. The client login authorization method comprises the following steps:

[0046] Step 301, in response to receiving a login authorization request sent by a client, parse out the client login identification code and user information contained in the login authorization request.

[0047] In some embodiments, the execution subject of the client login authorization method (e.g., service component 102) can parse the client login identification code and user information contained in the above login authorization request in response to receiving the login authorization request sent by the client. The client login identification code can be an identification code generated by the service component to uniquely identify the client. The user information can be the account information of the user who logged in to the client. For example, the user information can include: user name, account number. Among them, the login authorization request can refer to a request to log in to the service component.

[0048] Optionally, before step 301, the method further includes:

[0049] In the first step, in response to receiving a component configuration request sent by the client, client configuration information corresponding to the client is generated according to the component configuration request. The component configuration can be performed according to the component configuration request to obtain the client configuration information. For example, the client configuration information can be information such as the configured page main body color, sensitive copy, etc.

[0050] The second step is to generate a client login identification code corresponding to the client in response to the completion of the configuration of the client configuration information. For example, the client login identification code of the client can be randomly generated.

[0051] Step 302: Read the client configuration information corresponding to the client login identification code.

[0052] In some embodiments, the execution subject may read the client configuration information corresponding to the client login identification code. That is, the client login identification code may be used to query whether the client has configured the client configuration information locally. The client configuration information may refer to the information requested by the client for configuration. For example, the client configuration information may be the configuration of the main color of the page, the customization of sensitive text, etc.

[0053] Step 303: in response to reading the client configuration information corresponding to the client login identification code, verify the user information.

[0054] In some embodiments, the execution subject may verify the user information in response to reading the client configuration information corresponding to the client login identification code. For example, the user name or account included in the user information may be verified. It may be detected whether the user name or account included in the user information has been registered.

[0055] Step 304, in response to the user information being verified, generating a component interface transfer protocol service link according to the user information, and sending the component interface transfer protocol service link to the client.

[0056] In some embodiments, the execution subject may generate a component interface transfer protocol service link according to the user information in response to the user information verification being passed, and send the component interface transfer protocol service link to the client. The component interface transfer protocol service link may refer to an HTTP link. That is, the execution subject may directly generate a component interface transfer protocol service link containing the user information.

[0057] In some optional implementations of some embodiments, the execution subject may generate a component interface transfer protocol service link by following the steps below:

[0058] The first step is to encrypt the user information according to a preset symmetric key to generate encrypted user information. That is, the user information can be symmetrically encrypted by a symmetric key to generate encrypted user information.

[0059] The second step is to generate an initial component interface transfer protocol service link based on the encrypted user information, that is, an initial component interface transfer protocol service link (HTTP link) containing the encrypted user information can be generated.

[0060] The third step is to encrypt the symmetric key to generate an encrypted symmetric key. For example, the symmetric key can be asymmetrically encrypted to generate an encrypted symmetric key.

[0061] In the fourth step, the encrypted symmetric key and the associated component domain name are added to the initial component interface transfer protocol service link to obtain the component interface transfer protocol service link. The component domain name may refer to the domain name of the service component.

[0062] Optionally, the component interface transmission protocol service link carries encrypted user information.

[0063] Optionally, in response to detecting an access operation of the client accessing the component interface transfer protocol service link, the encrypted user information contained in the component interface transfer protocol service link is decrypted to obtain the decrypted user information.

[0064] In some embodiments, the execution subject may, in response to detecting an access operation of the client accessing the component interface transmission protocol service link, decrypt the encrypted user information contained in the component interface transmission protocol service link to obtain the decrypted user information. That is, the access operation may refer to an operation of the client clicking on the component interface transmission protocol service link. That is, the encrypted user information contained in the component interface transmission protocol service link may be decrypted according to the encrypted symmetric key included in the component interface transmission protocol service link to obtain the decrypted user information.

[0065] Optionally, write the login state corresponding to the above decrypted user information.

[0066] In some embodiments, the execution subject may write the login state corresponding to the decrypted user information. That is, the execution subject may write the decrypted user information into a cookie and save the login state in JWT (Json Web Token).

[0067] Optionally, in response to the above-mentioned login state being written successfully, a component service page is pushed to the above-mentioned client.

[0068] In some embodiments, the execution subject may push a component service page to the client in response to the successful writing of the login state, that is, the SaaS component service page may be pushed to the client.

[0069] from Figure 3 It can be seen that Figure 3 The process 300 in some corresponding embodiments solves the cross-domain login state problem of SaaS components, does not need to maintain a central authorization service, and the access method is more lightweight. It realizes the overall login authorization of the client and supports the client to customize the component products.

[0070] Further references Figure 4 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a component login device. These device embodiments are similar to Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various electronic devices.

[0071] like Figure 4 As shown, the component login device 400 of some embodiments includes: a first sending unit 401, a second sending unit 402 and a jump unit 403. The first sending unit 401 is configured to send a component configuration request to the associated service component; the second sending unit 402 is configured to respond to receiving a client login identification code corresponding to the component configuration request sent by the service component, and send a login authorization request to the service component through a remote call interface, wherein the login authorization request carries the client login identification code and user information; the jump unit 403 is configured to respond to receiving a component interface transmission protocol service link corresponding to the login authorization request sent by the service component, and jump to the component service page pointed to by the component interface transmission protocol service link.

[0072] It is understood that the units described in the device 400 are similar to those described in the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the device 400 and the units included therein, and will not be described in detail here.

[0073] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a client login authorization device. These client login authorization device embodiments are similar to Figure 3 Corresponding to the method embodiments shown, the client login authorization device can be specifically applied to various electronic devices.

[0074] like Figure 5 As shown, the client login authorization device 500 of some embodiments includes: a parsing unit 501, a reading unit 502, a verification unit 503 and a generating unit 504. The parsing unit 501 is configured to parse out the client login identification code and user information contained in the login authorization request in response to receiving the login authorization request sent by the client; the reading unit 502 is configured to read the client configuration information corresponding to the client login identification code; the verification unit 503 is configured to verify the user information in response to reading the client configuration information corresponding to the client login identification code; the generating unit 504 is configured to generate a component interface transmission protocol service link according to the user information in response to the verification of the user information being passed, and send the component interface transmission protocol service link to the client corresponding to the login authorization request sent by the service component.

[0075] Optionally, the component interface transmission protocol service link carries encrypted user information.

[0076] Optionally, the client login authorization device 500 also includes: a decryption unit, configured to, in response to detecting an access operation of the client accessing the component interface transmission protocol service link, decrypt the encrypted user information contained in the above-mentioned component interface transmission protocol service link to obtain decrypted user information; a writing unit, configured to: write the login state corresponding to the above-mentioned decrypted user information; and a pushing unit, configured to push the component service page to the above-mentioned client in response to the successful writing of the above-mentioned login state.

[0077] Optionally, the generation unit 504 is further configured to: encrypt the above-mentioned user information according to a preset symmetric key to generate encrypted user information; generate an initial component interface transfer protocol service link according to the above-mentioned encrypted user information; encrypt the above-mentioned symmetric key to generate an encrypted symmetric key; add the above-mentioned encrypted symmetric key and the associated component domain name to the above-mentioned initial component interface transfer protocol service link to obtain the component interface transfer protocol service link.

[0078] Optionally, before the parsing unit 501, the client login authorization device 500 also includes: an information generation unit, configured to generate client configuration information corresponding to the above-mentioned client in response to receiving a component configuration request sent by the above-mentioned client according to the above-mentioned component configuration request; an identification code generation unit, configured to generate a client login identification code corresponding to the above-mentioned client in response to the completion of the configuration of the above-mentioned client configuration information.

[0079] It is understandable that the various units recorded in the client login authorization device 500 are similar to the reference Figure 3 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the client login authorization device 500 and the units contained therein, and will not be described in detail here.

[0080] Reference below Figure 6 , which shows an electronic device (eg, Figure 1 The electronic devices in some embodiments of the present disclosure may include but are not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, AR / VR / MR devices, etc. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0081] like Figure 6 As shown, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0082] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 6 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0083] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.

[0084] It should be noted that the computer-readable medium recorded in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0085] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0086] The computer-readable medium may be included in the electronic device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: sends a component configuration request to the associated service component; in response to receiving the client login identification code corresponding to the component configuration request sent by the service component, sends a login authorization request to the service component through a remote call interface, wherein the login authorization request carries the client login identification code and user information; in response to receiving the component interface transmission protocol service link corresponding to the login authorization request sent by the service component, jumps to the component service page pointed to by the component interface transmission protocol service link.

[0087] Or enable the electronic device to: in response to receiving a login authorization request sent by the client, parse out the client login identification code and user information contained in the above login authorization request; read the client configuration information corresponding to the above client login identification code; in response to reading the client configuration information corresponding to the above client login identification code, verify the above user information; in response to the above user information verification being passed, generate a component interface transfer protocol service link based on the above user information, and send the above component interface transfer protocol service link to the above client.

[0088] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0089] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0090] The units described in some embodiments of the present disclosure may be implemented by software or by hardware. The described units may also be set in a processor, for example, may be described as: a processor comprising: a first sending unit, a second sending unit and a jump unit. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances. For example, the jump unit may also be described as "a unit that jumps to the component service page pointed to by the above-mentioned component interface transmission protocol service link in response to receiving the component interface transmission protocol service link corresponding to the above-mentioned login authorization request sent by the above-mentioned service component."

[0091] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0092] Some embodiments of the present disclosure further provide a computer program product, including a computer program, which implements any of the above-mentioned component login methods when executed by a processor.

[0093] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.

Claims

1. A component login method, include: Sending a component configuration request to the associated service component; In response to receiving the client login identification code corresponding to the component configuration request sent by the service component, sending a login authorization request to the service component through a remote call interface, wherein the login authorization request carries the client login identification code and user information; In response to receiving the component interface transmission protocol service link corresponding to the login authorization request sent by the service component, jump to the component service page pointed to by the component interface transmission protocol service link.

2. A client login authorization method, include: In response to receiving a login authorization request sent by a client, parsing the client login identification code and user information contained in the login authorization request; Read the client configuration information corresponding to the client login identification code; In response to reading the client configuration information corresponding to the client login identification code, verifying the user information; In response to the user information being verified, a component interface transfer protocol service link is generated according to the user information, and the component interface transfer protocol service link is sent to the client.

3. The method according to claim 2, in, The component interface transfer protocol service link carries encrypted user information; as well as The method further comprises: In response to detecting an access operation of the client accessing the component interface transfer protocol service link, decrypting the encrypted user information contained in the component interface transfer protocol service link to obtain decrypted user information; Write the login state corresponding to the decrypted user information; In response to the login state being written successfully, a component service page is pushed to the client.

4. The method according to claim 2, in, The generating a component interface transmission protocol service link according to the user information includes: Encrypting the user information according to a preset symmetric key to generate encrypted user information; Generating an initial component interface transfer protocol service link based on the encrypted user information; Encrypting the symmetric key to generate an encrypted symmetric key; The encrypted symmetric key and the associated component domain name are added to the initial component interface transfer protocol service link to obtain a component interface transfer protocol service link.

5. The method according to claim 2, in, Before the step of parsing the client login identification code and user information contained in the login authorization request sent by the service component in response to receiving the login authorization request sent by the service component, the method further includes: In response to receiving a component configuration request sent by the client, generating client configuration information corresponding to the client according to the component configuration request; In response to the completion of configuration of the client configuration information, a client login identification code corresponding to the client is generated.

6. A component login device, include: A first sending unit, configured to send a component configuration request to an associated service component; The second sending unit is configured to send a login authorization request to the service component through a remote call interface in response to receiving a client login identification code corresponding to the component configuration request sent by the service component, wherein the login authorization request carries the client login identification code and user information; The jump unit is configured to jump to the component service page pointed to by the component interface transmission protocol service link in response to receiving the component interface transmission protocol service link corresponding to the login authorization request sent by the service component.

7. A client login authorization device, include: A parsing unit, configured to parse out the client login identification code and user information contained in the login authorization request in response to receiving the login authorization request sent by the client; A reading unit, configured to read the client configuration information corresponding to the client login identification code; a verification unit, configured to verify the user information in response to reading the client configuration information corresponding to the client login identification code; The generating unit is configured to generate a component interface transmission protocol service link according to the user information in response to the user information being verified, and send the component interface transmission protocol service link to the client corresponding to the login authorization request sent by the service component.

8. An electronic device, include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as claimed in any one of claims 1 or 2-5.

9. A computer readable medium having a computer program stored thereon, in, When the program is executed by a processor, the method according to any one of claims 1 or 2-5 is implemented.

10. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 or 2-5.

Images