WO2023092316A1 - 一种第三方服务登录方法、装置、终端设备及存储介质 - Google Patents

一种第三方服务登录方法、装置、终端设备及存储介质 Download PDF

Info

Publication number
WO2023092316A1
WO2023092316A1 PCT/CN2021/132684 CN2021132684W WO2023092316A1 WO 2023092316 A1 WO2023092316 A1 WO 2023092316A1 CN 2021132684 W CN2021132684 W CN 2021132684W WO 2023092316 A1 WO2023092316 A1 WO 2023092316A1
Authority
WO
WIPO (PCT)
Prior art keywords
party service
user
target
token
service
Prior art date
Application number
PCT/CN2021/132684
Other languages
English (en)
French (fr)
Inventor
莫佩红
季统凯
贺忠堂
Original Assignee
国云科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 国云科技股份有限公司 filed Critical 国云科技股份有限公司
Priority to PCT/CN2021/132684 priority Critical patent/WO2023092316A1/zh
Publication of WO2023092316A1 publication Critical patent/WO2023092316A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • G06F21/41User authentication where a single sign-on provides access to a plurality of computers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the embodiments of the present application relate to the field of multi-cloud platforms, and in particular to a third-party service login method, device, terminal equipment, and storage medium.
  • Embodiments of the present invention provide a third-party service login method, device, terminal equipment, and storage medium, which solves the problem that users cannot log in and manage SaaS service systems and cloud applications in a multi-cloud management platform in a unified manner in the prior art, resulting in A technical problem with complex and inefficient login operations.
  • the embodiment of the present invention provides a third-party service login method, including the following steps:
  • the target third-party service is invoked to realize corresponding functions.
  • the specific process of registering a third-party service is as follows:
  • the user invokes the target third-party service
  • jump to the target third-party service and use the cloud platform token as the third-party service token to be verified.
  • the specific process is as follows:
  • the service call instruction sent by the user call the target third-party service in the form of Http call, and use the cloud platform token as the third-party service token to be verified, and the service call instruction contains the target Identification information for third-party services.
  • the specific process of verifying the third-party service token according to the verification request of the target third-party service is as follows:
  • the third-party service token is the cloud platform token of the user.
  • the authentication passing information includes identification information of the target third-party service and pre-stored user identification information of the user.
  • the specific process of enabling the target third-party service to complete the user's login according to the authentication passing information is as follows:
  • Make the target third-party service determine that the third-party service token has passed the verification according to the identification information in the authentication passing information, obtain the user information of the user according to the user identification information, and obtain the user information according to the user information Create and log in said user.
  • the specific process of invoking the target third-party service to realize corresponding functions according to the third-party service instruction sent by the user is as follows:
  • the interface of the target third-party service is called, so that the target third-party service realizes a corresponding function.
  • an embodiment of the present invention provides a third-party service login device, including a service registration module, a token generation module, a verification module, a user login module, and a service call module;
  • the service registration module is used to register third-party services
  • the token generating module is used to log in the user and generate the user's cloud platform token according to the user's login request;
  • the verification module is used to jump to the target third-party service when the user invokes the target third-party service, and use the cloud platform token as the third-party service token to be verified, according to the target A verification request from a third-party service, verifying the third-party service token;
  • the user login module is configured to return authentication passing information to the target third-party service if the verification is successful, so that the target third-party service completes the user's login according to the authentication passing information;
  • the service calling module is used to call the target third-party service to realize corresponding functions according to the third-party service usage instruction sent by the user.
  • an embodiment of the present invention provides a terminal device, where the terminal device includes a processor and a memory;
  • the memory is used to store a computer program and transmit the computer program to the processor
  • the processor is configured to execute a third-party service login method as described in the first aspect according to instructions in the computer program.
  • an embodiment of the present invention provides a storage medium storing computer-executable instructions, and the computer-executable instructions are used to perform a third-party service login as described in the first aspect when executed by a computer processor. method.
  • the embodiment of the present invention provides a third-party service login method, device, terminal equipment and storage medium, the method includes registering a third-party service; according to the user's login request, logging in the user and generating the user's cloud platform token;
  • the target third-party service jump to the target third-party service, use the cloud platform token as the third-party service token to be verified, and verify the third-party service token according to the verification request of the target third-party service; If the verification is successful, return the authentication passing information to the target third-party service, so that the target third-party service can complete the user's login according to the authentication passing information; call the target third-party service to realize the corresponding according to the third-party service instruction sent by the user Function.
  • the multi-cloud platform when a user logs in to the multi-cloud platform, the multi-cloud platform will generate the user's cloud platform token, and when the subsequent user calls the target third-party service, the cloud platform token will be used as the third-party service token to be verified,
  • the multi-cloud platform verifies the third-party service token; if the verification is successful, the target third-party service can complete the user's login on its own system, so that the user can log in to the third-party service through the multi-cloud platform.
  • FIG. 1 is a flowchart of a third-party service login method provided by an embodiment of the present invention.
  • Fig. 2 is a schematic diagram of interaction between a multi-cloud platform and a third-party service provided by an embodiment of the present invention.
  • Fig. 3 is a schematic structural diagram of a third-party service login device provided by an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a terminal device provided by an embodiment of the present invention.
  • FIG. 1 is a flowchart of a third-party service login method provided by an embodiment of the present invention.
  • the third-party service login method provided by the embodiment of the present invention can be executed by a third-party service login device, which can be implemented by software and/or hardware, and the third-party service login device can be two or more It is composed of physical entities, and can also be composed of a physical entity.
  • the third-party service login device may be a computer, a host computer, a tablet, or a server.
  • the method includes the following steps:
  • Step 101 register a third-party service.
  • the third-party service needs to be registered on the multi-cloud platform, so as to connect the third-party service to the multi-cloud platform, so that the multi-cloud platform can call the third-party service.
  • the third-party service is a SaaS service.
  • the specific process of registering a third-party service is as follows:
  • a third-party service wants to access the multi-cloud platform, it needs to provide its own access information to the multi-cloud platform.
  • the multi-cloud platform After receiving the access information, the multi-cloud platform registers the third-party service according to the access information and generates the identification information of the third-party service , the identification information is the unique identification of the third-party service on the multi-cloud platform.
  • the third-party service is a SaaS service
  • the access information includes the system access address, port, and name of the SaaS service system.
  • the multi-cloud platform After receiving the access information, the multi-cloud platform registers the third-party service, and generates the first The identification information AppAppId of the third-party service, and the access information is saved in the database in the form of JSON, which can adapt to the access requirements of different SaaS service systems.
  • the access information of a certain third-party service system access address, port, and SaaS service system name are submitted and saved in JSON form as follows:
  • AppAddress is the system access address
  • AppName is the name of the SaaS service system.
  • Step 102 log in the user and generate the user's cloud platform token.
  • the multi-cloud platform When a user logs in to the multi-cloud platform, the multi-cloud platform will receive the user's login request, and the multi-cloud platform will log in the user according to the login request, and generate the user's cloud platform token on the multi-cloud platform.
  • Step 103 when the user calls the target third-party service, jump to the target third-party service, use the cloud platform token as the third-party service token to be verified, and verify the third-party service token according to the verification request of the target third-party service The card is verified.
  • the target third-party service After the user logs in to the multi-cloud platform, when the user needs to use the target third-party service, click the target third-party service on the display interface of the multi-cloud platform to jump to the target third-party service. In the process of jumping to the target third-party service , use the user's cloud platform token on the multi-cloud platform as the third-party service token to be verified.
  • the target third-party service After the target third-party service is called, it sends a verification request to the multi-cloud platform.
  • the multi-cloud platform sends the verification request according to the target third-party service. Verify the third-party service token.
  • the target third-party service invokes the multi-cloud platform in the form of an Http call to send a verification request to the multi-cloud platform, thereby triggering the multi-cloud platform to verify the third-party service token to be verified.
  • the target third-party service is called in the form of Http call, and the cloud platform token is used as the third-party service token to be verified.
  • the service call instruction contains the identification information of the target third-party service.
  • a service call instruction is sent to the multi-cloud platform, and the service call instruction includes identification information of the target third-party service.
  • the multi-cloud platform will receive a service call instruction including identification information of the target third-party service.
  • the multi-cloud platform calls the target third-party service in the form of Http call according to the identification information in the service call instruction, and uses the user's cloud platform token as the third-party service to be verified during the call process token.
  • StoreSystemAddress is the access address of the target SaaS service system
  • Cmptoken is the cloud platform token of the user on the multi-cloud platform
  • token is the SaaS service system token to be verified
  • AppAppId is the unique identifier of the target SaaS service system on the multi-cloud platform
  • appId It is the identification of the SaaS service system to be invoked.
  • the specific process of verifying the third-party service token is as follows:
  • the verification request of the target third-party service determine whether the third-party service token is the user's cloud platform token.
  • the multi-cloud platform needs to be triggered to verify the third-party service token to be verified. After the multi-cloud platform is triggered, it determines whether the third-party service token to be verified is the one generated by its own system before The user's cloud platform token, if yes, the verification is successful, if not, the verification fails.
  • the target SaaS service calls the multi-cloud platform in the form of Http, so that the multi-cloud platform verifies the third-party service token, and the specific calling address is:
  • CmpAddress is the access address of the multi-cloud platform
  • verifyToken is the method for verifying the token of the multi-cloud platform. Verify, if they are the same, the verification is passed, if not, the verification is not passed.
  • Step 104 If the verification is successful, return the authentication passing information to the target third-party service, so that the target third-party service completes the user's login according to the authentication passing information.
  • the multi-cloud platform If the multi-cloud platform successfully verifies the third-party token, it will send authentication passing information to the target third-party service. After receiving the authentication passing information, the target third-party service will confirm that the third-party service token has passed the verification and obtain the current login to the multi-cloud platform. The user information of the user and create a user to complete the user login process.
  • the authentication passing information includes identification information of the target third-party service and pre-stored user identification information of the user.
  • the multi-cloud platform If the multi-cloud platform passes the verification of the third-party service token, it will send authentication passing information to the target third-party service.
  • the authentication passing information includes the identification information of the target third-party service that called the multi-cloud platform and the current login account User ID information for the user.
  • the user identification information is pre-stored on the multi-cloud platform, and the user identification information is generated when the user registers to the multi-cloud platform. It can be understood that the user identification information is a unique credential for distinguishing different users.
  • the specific process for the target third-party service to complete the user's login according to the authentication passing information is as follows:
  • the target third-party service determines that the third-party service token has passed the verification according to the identification information in the authentication pass information, obtains the user information of the user according to the user identification information, and creates and logs in the user according to the user information.
  • the target third-party service after receiving the authentication pass information, determines that its own third-party service token has passed the verification according to the identification information in the authentication pass information, and then, it can Identification information, to obtain pre-stored user information from the multi-cloud platform.
  • the user identification information is a user ID.
  • User information includes but not limited to user ID, user name, user role, role logo, department, unit, and phone number. User information is provided by the user when the user registers to the multi-cloud platform Provided, and the multi-cloud platform will store user information.
  • the target third-party service After the target third-party service obtains the corresponding user information, it creates a corresponding user in its own system according to the user information, and completes the synchronization of the user on the multi-cloud platform to the target third-party service. After the synchronization is completed, log in the user according to the user identification information , at this point, the process of the user logging in to the target third-party service from the multi-cloud platform is completed.
  • Step 105 Call the target third-party service to realize the corresponding function according to the third-party service usage instruction sent by the user.
  • the user can use the target third-party service on the multi-cloud platform.
  • the user needs to use the target third-party service, send the third-party service instruction to the multi-cloud platform.
  • the multi-cloud platform After receiving the third-party service instruction, the multi-cloud platform calls the target third-party service according to the third-party service instruction, so that the third-party service can complete the corresponding function.
  • the interaction between the multi-cloud platform and third-party services is shown in Figure 2.
  • the specific process of invoking the target third-party service to realize the corresponding function is as follows:
  • the interface of the target third-party service is called, so that the target third-party service can realize the corresponding function.
  • the multi-cloud platform After receiving the third-party service instruction sent by the user, the multi-cloud platform calls the interface of the target third-party service, so that the target third-party service can realize the function operated by the user.
  • the multi-cloud platform uses a RESTful API conforming to the REST design style to directly call interfaces of functions/functions encapsulated by major SaaS service systems to complete corresponding functions.
  • RESTful API is defined from the following three aspects:
  • Transferred resources Internet media types accepted and returned by Web services, such as JSON, XML, etc.
  • Operations on resources a series of request methods supported by the Web service on the resource (for example: POST, GET, PUT or DELETE).
  • the request message style and response message style are as follows:
  • the user information scattered in various third-party services can also be integrated and stored in the multi-cloud platform, and the user information can be managed uniformly through the multi-cloud platform, specifying which properties of the user need to perform which operations. Auditing, unified management of user processes, when an employee leaves or transfers, all third-party service adjustments can also be completed with one configuration.
  • the embodiment of the present invention provides a third-party service login method.
  • the multi-cloud platform When the user logs in to the multi-cloud platform, the multi-cloud platform will generate the user's cloud platform token, and when the subsequent user calls the target third-party service, the cloud platform token The card is used as the third-party service token to be verified, and the third-party service token is verified; if the verification is successful, the target third-party service can complete the user's login on its own system, so that the user can log in through the multi-cloud platform Logging in to third-party services, users only need a set of user names and passwords to access the cloud resources of major cloud vendors and the company's own third-party service systems without having to enter passwords again, reducing the complexity of frequent login operations for users; In the prior art, the user cannot log in and manage the SaaS service system and the cloud application in a unified way in the multi-cloud management platform, which leads to the technical problem that the login operation is complicated and inefficient.
  • Figure 3 is a schematic structural diagram of a third-party service login device provided by an embodiment of the present invention, including a service registration module 201, a token generation module 202, a verification module 203, a user login module 204, and a service call module 205;
  • the service registration module 201 is used for registering third-party services
  • the token generation module 202 is used for logging in the user and generating the cloud platform token of the user according to the login request of the user;
  • the verification module 203 is used to jump to the target third-party service when the user invokes the target third-party service, use the cloud platform token as the third-party service token to be verified, and perform the verification request of the target third-party service according to the verification request of the target third-party service.
  • the three-party service token is verified;
  • the user login module 204 is used to return authentication passing information to the target third-party service if the verification is successful, so that the target third-party service completes the user's login according to the authentication passing information;
  • the service calling module 205 is used to call the target third-party service to realize the corresponding function according to the third-party service usage instruction sent by the user.
  • the service registration module 201 is used to register third-party services specifically as follows:
  • It is used to receive the access information of the third-party service, register the third-party service according to the access information, and generate the identification information of the third-party service.
  • the verification module 203 is used to jump to the target third-party service when the user invokes the target third-party service, and use the cloud platform token as the third-party service token to be verified. Specifically:
  • the service call command contains the identification information of the target third-party service .
  • the verification module 203 is configured to verify the third-party service token according to the verification request of the target third-party service, specifically:
  • the authentication passing information includes identification information of the target third-party service and pre-stored user identification information of the user.
  • the user login module 204 is used to enable the target third-party service to complete the user's login according to the authentication passing information, specifically:
  • the service calling module 205 is used to call the target third-party service to realize corresponding functions according to the third-party service usage instruction sent by the user, specifically:
  • It is used to call the interface of the target third-party service according to the third-party service instruction sent by the user, so that the target third-party service can realize the corresponding function.
  • This embodiment also provides a terminal device, as shown in FIG. 4 , a terminal device 30, the terminal device includes a processor 300 and a memory 301;
  • the memory 301 is used to store a computer program 302, and transmit the computer program 302 to the processor;
  • the processor 300 is configured to execute the steps in the embodiment of the above-mentioned third-party service login method according to the instructions in the computer program 302 .
  • the computer program 302 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 301 and executed by the processor 300 to complete this application.
  • the one or more modules/units may be a series of computer program instruction segments capable of accomplishing specific functions, and the instruction segments are used to describe the execution process of the computer program 302 in the terminal device 30 .
  • the terminal device 30 may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server.
  • the terminal device 30 may include, but not limited to, a processor 300 and a memory 301 .
  • FIG. 4 is only an example of the terminal device 30, and does not constitute a limitation on the terminal device 30. It may include more or less components than those shown in the figure, or combine certain components, or different components.
  • the terminal device 30 may also include an input and output device, a network access device, a bus, and the like.
  • the so-called processor 300 may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, and the like.
  • the storage 301 may be an internal storage unit of the terminal device 30 , for example, a hard disk or a memory of the terminal device 30 .
  • the memory 301 can also be an external storage terminal device of the terminal device 30, such as a plug-in hard disk equipped on the terminal device 30, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD ) card, flash memory card (Flash Card), etc. Further, the memory 301 may also include both an internal storage unit of the terminal device 30 and an external storage device.
  • the memory 301 is used to store the computer program and other programs and data required by the terminal device 30 .
  • the memory 301 can also be used to temporarily store data that has been output or will be output.
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present invention.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc and other media that can store computer programs. .
  • An embodiment of the present invention also provides a storage medium containing computer-executable instructions, the computer-executable instructions are used to execute a third-party service login method when executed by a computer processor, and the method includes the following steps:
  • the target third-party service According to the third-party service instruction sent by the user, call the target third-party service to realize the corresponding function.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明实施例公开了一种第三方服务登录方法、装置、终端设备及存储介质,方法包括注册第三方服务;根据用户的登录请求,登录用户并生成用户的云平台令牌;当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌,根据目标第三方服务的验证请求,对第三方服务令牌进行校验;若校验成功,向目标第三方服务返回认证通过信息,以使目标第三方服务根据认证通过信息,完成用户的登录;根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能。本发明实施例解决了现有技术中用户无法在多云管理平台中对SaaS服务系统和上云应用统一进行登录和管理,导致登录操作复杂且效率低下的技术问题。

Description

一种第三方服务登录方法、装置、终端设备及存储介质 技术领域
本申请实施例涉及多云平台领域,尤其涉及一种第三方服务登录方法、装置、终端设备及存储介质。
背景技术
目前,随着科学技术的不断发展,云计算技术也愈加先进。现在市面上很多企业的应用都已经上云,企业通过使用多个云厂商提供的云服务,并且在云服务上部署SaaS(Software-as-a-Service,软件即服务)服务系统以支撑自身业务的运作。
企业在使用云服务的过程中,需要使用多云管理平台对不同云厂商的云服务进行管理,但是由于企业自身的SaaS服务系统并没有接入到多元管理平台,在实际使用过程中,用户需要分别登录SaaS服务系统和上云应用,之后再分别对SaaS服务系统和上云应用进行管理,无法在多云管理平台中对SaaS服务系统和上云应用统一进行登录和管理,导致登录操作复杂且效率低下。
发明内容
本发明实施例提供了一种第三方服务登录方法、装置、终端设备及存储介质,解决了现有技术中用户无法在多云管理平台中对SaaS服务系统和上云应用统一进行登录和管理,导致登录操作复杂且效率低下的技术问题。
第一方面,本发明实施例提供了一种第三方服务登录方法,包括以下步骤:
注册第三方服务;
根据用户的登录请求,登录所述用户并生成所述用户的云平台令牌;
当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌,根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验;
若校验成功,向所述目标第三方服务返回认证通过信息,以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录;
根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能。
优选的,所述注册第三方服务的具体过程为:
接收第三方服务的接入信息,根据所述接入信息注册所述第三方服务,生成所述第三方服务的标识信息。
优选的,所述当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌的具体过程为:
根据所述用户发送的服务调用指令,以Http调用形式调用所述目标第三方服务,并将所述云平台令牌作为待校验的第三方服务令牌,所述服务调用指令中包含有目标第三方服务的标识信息。
优选的,所述根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验的具体过程为:
所述根据所述目标第三方服务的验证请求,判断所述第三方服务令牌是否为所述用户的云平台令牌。
优选的,所述认证通过信息包括所述目标第三方服务的标识信息以及预先储存的所述用户的用户标识信息。
优选的,所述以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录的具体过程为:
以使所述目标第三方服务根据所述认证通过信息中的标识信息,确定所述第三方服务令牌通过验证,根据所述用户标识信息,获取所述用户的用户信息,根据所述用户信息创建并登录所述用户。
优选的,所述根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能的具体过程为:
根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务的接口,以使所述目标第三方服务实现相应的功能。
第二方面,本发明实施例提供了一种第三方服务登录装置,包括服务注册模块、令牌生成模块、校验模块、用户登录模块以及服务调用模块;
所述服务注册模块用于注册第三方服务;
所述令牌生成模块用于根据用户的登录请求,登录所述用户并生成所述用 户的云平台令牌;
所述校验模块用于当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌,根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验;
所述用户登录模块用于若校验成功,向所述目标第三方服务返回认证通过信息,以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录;
所述服务调用模块用于根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能。
第三方面,本发明实施例提供了一种终端设备,所述终端设备包括处理器以及存储器;
所述存储器用于存储计算机程序,并将所述计算机程序传输给所述处理器;
所述处理器用于根据所述计算机程序中的指令执行如第一方面所述的一种第三方服务登录方法。
第四方面,本发明实施例提供了一种存储计算机可执行指令的存储介质,所述计算机可执行指令在由计算机处理器执行时用于执行如第一方面所述的一种第三方服务登录方法。
上述,本发明实施例提供了一种第三方服务登录方法、装置、终端设备及存储介质,方法包括注册第三方服务;根据用户的登录请求,登录用户并生成用户的云平台令牌;当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌,根据目标第三方服务的验证请求,对第三方服务令牌进行校验;若校验成功,向目标第三方服务返回认证通过信息,以使目标第三方服务根据认证通过信息,完成用户的登录;根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能。
本发明实施例当用户登录到多云平台时,多云平台会生成用户的云平台令牌,并且在后续用户调用目标第三方服务时,将云平台令牌作为待校验的第三方服务令牌,多云平台对第三方服务令牌进行校验;若校验成功,则目标第三方服务能够在自身系统上完成用户的登录,从而使得用户通过多云平台即可登录到第三方服务上,用户只要一套用户名、密码,即可通访问各大云厂商云资源及企业自身第三方服务系统,而无须再次输入密码,降低用户频繁登陆操作 的复杂性,解决了现有技术中用户无法在多云管理平台中对SaaS服务系统和上云应用统一进行登录和管理,导致登录操作复杂且效率低下的技术问题。
附图说明
图1为本发明实施例提供的一种第三方服务登录方法的流程图。
图2为本发明实施例提供的一种多云平台和第三方服务的交互示意图。
图3为本发明实施例提供的一种第三方服务登录装置的结构示意图。
图4为本发明实施例提供的一种终端设备的结构示意图。
具体实施方式
以下描述和附图充分地示出本申请的具体实施方案,以使本领域的技术人员能够实践它们。实施例仅代表可能的变化。除非明确要求,否则单独的部件和功能是可选的,并且操作的顺序可以变化。一些实施方案的部分和特征可以被包括在或替换其他实施方案的部分和特征。本申请的实施方案的范围包括权利要求书的整个范围,以及权利要求书的所有可获得的等同物。在本文中,各实施方案可以被单独地或总地用术语“发明”来表示,这仅仅是为了方便,并且如果事实上公开了超过一个的发明,不是要自动地限制该应用的范围为任何单个发明或发明构思。本文中,诸如第一和第二等之类的关系术语仅仅用于将一个实体或者操作与另一个实体或操作区分开来,而不要求或者暗示这些实体或操作之间存在任何实际的关系或者顺序。而且,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法或者终端设备不仅包括那些要素,而且还包括没有明确列出的其他要素。本文中各个实施例采用递进的方式描述,每个实施例重点说明的都是与其他实施例的不同之处,各个实施例之间相同相似部分互相参见即可。对于实施例公开的结构、产品等而言,由于其与实施例公开的部分相对应,所以描述的比较简单,相关之处参见方法部分说明即可。
实施例一
如图1所示,图1为本发明实施例提供的一种第三方服务登录方法的流程图。本发明实施例提供的第三方服务登录方法可以由第三方服务登录设备执行, 该第三方服务登录设备可以通过软件和/或硬件的方式实现,该第三方服务登录设备可以是两个或多个物理实体构成,也可以由一个物理实体构成。例如第三方服务登录设备可以是电脑、上位机、平板以及服务器等设备。方法包括以下步骤:
步骤101、注册第三方服务。
在本实施例中,首先需要将第三方服务注册到多云平台上,从而将第三方服务接入到多云平台中,使得多云平台能够调用第三方服务。在一个实施例中,第三方服务为SaaS服务。
在一个实施例中,注册第三方服务的具体过程为:
接收第三方服务的接入信息,根据接入信息注册第三方服务,生成第三方服务的标识信息。
第三方服务若要接入到多云平台上,需要提供自身的接入信息给多云平台,多云平台在接收到接入信息后,根据接入信息注册第三方服务,并生成第三方服务的标识信息,该标识信息为第三方服务在多云平台上的唯一标识。示例性的,在一个实施例中,第三方服务为SaaS服务,接入信息包括系统访问地址、端口以及SaaS服务系统名称等,多云平台在接收到接入信息后注册第三方服务,并生成第三方服务的标识信息AppAppId,并将接入信息以JSON的形式保存在数据库中,以JSON形式保存可适配不同SaaS服务系统的接入要求。
示例性的,在一个实施例中某一第三方服务的接入信息:系统访问地址、端口、SaaS服务系统名称提交后,以JSON形式保存如下:
{"AppAppId":"18dca19c5dba42afae4c08d3a970770a","AppAddress":"http://StoreSystemAddress:5000","AppName":"StoreSystemName"}
其中,AppAddress为系统访问地址,AppName为SaaS服务系统名称。
步骤102、根据用户的登录请求,登录用户并生成用户的云平台令牌。
当用户登录到多云平台时,多云平台会接受到用户的登录请求,多云平台则会根据登录请求,登录用户,并生成用户在多云平台上的云平台令牌。
步骤103、当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌,根据目标第三方服务的验证请求,对第三方服务令牌进行校验。
用户登录到多云平台后,当用户需要使用目标第三方服务时,在多云平台的显示界面上点击目标第三方服务即可跳转到目标第三方服务,在跳转到目标第三方服务的过程中,将用户在多云平台上的云平台令牌作为待校验的第三方服务令牌,目标第三方服务被调用后,向多云平台发送验证请求,多云平台根据目标第三方服务发送的验证请求,对第三方服务令牌进行校验。在一个实施例中,目标第三方服务以Http调用形式调用多云平台以向多云平台发送验证请求,从而触发多云平台对待校验的第三方服务令牌进行校验。
在上述实施例的基础上,当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌的具体过程为:
根据用户发送的服务调用指令,以Http调用形式调用目标第三方服务,并将云平台令牌作为待校验的第三方服务令牌,服务调用指令中包含有目标第三方服务的标识信息。
在一个实施例中,当用户需要调用目标第三方服务时,会向多云平台发送服务调用指令,服务调用指令中包括有目标第三方服务的标识信息。例如用户在多云平台的显示界面上点击目标第三方服务后,多云平台会接收到包含有目标第三方服务的标识信息的服务调用指令。多云平台在接收到服务调用指令后,根据服务调用指令中的标识信息,以Http调用形式调用目标第三方服务,并在调用过程中,将用户的云平台令牌作为待校验的第三方服务令牌。
示例性的,在一个实施例中,多云平台以Http调用形式调用目标SaaS服务为:以Http调用形式跳转到目标SaaS服务,调用地址以http://StoreSystemAddress?token=Cmptoken&appId=AppAppId方式。
其中,StoreSystemAddress为目标SaaS服务系统的访问地址,Cmptoken为用户在多云平台的云平台令牌,token为待校验的SaaS服务系统令牌,AppAppId为目标SaaS服务系统在多云平台的唯一标识,appId为所需要调用的SaaS服务系统的标识。在调用目标SaaS服务的过程中,令token=Cmptoken,appId=AppAppId。
在上述实施例的基础上,根据目标第三方服务的验证请求,对第三方服务令牌进行校验的具体过程为:
根据目标第三方服务的验证请求,判断第三方服务令牌是否为用户的云平 台令牌。
当目标第三方服务被调用后,需要触发多云平台对待校验的第三方服务令牌进行校验,多云平台被触发后,判断待校验的第三方服务令牌是否是之前自身系统生成的该用户的云平台令牌,若是,则校验成功,若否,则校验失败。在一个实施例中,目标SaaS服务以Http形式调用多云平台,从而使得多云平台对第三方服务令牌进行校验,具体的调用地址为:
http://CmpAddress/verifyToken?token=Cmptoken;
其中,CmpAddress为多云平台的访问地址,verifyToken为多云平台验证令牌的方法,多云平台通过判断第三方服务令牌token是否为用户在多云平台的云平台令牌Cmptoken,从而对第三方服务令牌进行验证,若相同,则验证通过,若不同,则验证不通过。
步骤104、若校验成功,向目标第三方服务返回认证通过信息,以使目标第三方服务根据认证通过信息,完成用户的登录。
如果多云平台对第三方令牌校验成功,则向目标第三方服务发送认证通过信息,目标第三方服务在接收到认证通过信息后,确认第三方服务令牌通过验证,获取当前登录到多云平台的用户的用户信息并创建用户,完成用户的登录过程。
在一个实施例中,认证通过信息包括目标第三方服务的标识信息以及预先储存的用户的用户标识信息。
若多云平台对第三方服务令牌校验通过后,会向目标第三方服务发送认证通过信息,其中,认证通过信息中包括了调用多云平台的目标第三方服务的标识信息以及当前登录多云平台的用户的用户标识信息。用户标识信息预先储存在多云平台上,且用户标识信息在用户注册到多云平台时生成,可理解,用户标识信息为区分不同用户的唯一凭证。
在上述实施例的基础上,以使目标第三方服务根据认证通过信息,完成用户的登录的具体过程为:
以使目标第三方服务根据认证通过信息中的标识信息,确定第三方服务令牌通过验证,根据用户标识信息,获取用户的用户信息,根据用户信息创建并登录用户。
在本实施例中,目标第三方服务在接收到认证通过信息后,根据认证通过信息中的标识信息,确定出自身的第三方服务令牌通过验证,之后,即可根据验证通过信息中的用户标识信息,从多云平台上获取预先储存的用户信息。在一个实施例中,用户标识信息为用户ID,用户信息包括但不仅限于用户ID、用户名称、用户角色、角色标志、所在部门、单位以及电话等,用户信息在用户注册到多云平台时由用户提供,并且多云平台会将用户信息进行储存。
目标第三方服务在获取到对应的用户信息后,根据用户信息在自身系统中创建对应的用户,完成多云平台上的用户到目标第三方服务的同步,同步完成后,根据用户标识信息,登录用户,此时,完成用户从多云平台登录到目标第三方服务的过程。
步骤105、根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能。
目标第三方服务在自身系统上登录用户后,用户即可在多云平台上使用目标第三方服务。当用户需要使用目标第三方服务时,向多云平台发送第三方服务使用指令,多云平台接收到第三方服务使用指令后,根据第三方服务指令调用目标第三方服务,使得第三方服务完成相应的功能,多云平台和第三方服务之间的交互如图2所示。
在一个实施例中,根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能的具体过程为:
根据用户发送的第三方服务使用指令,调用目标第三方服务的接口,以使目标第三方服务实现相应的功能。
多云平台接收到用户发送的第三方服务使用指令后,调用目标第三方服务的接口,使得目标第三方服务能够实现用户所操作的功能。在一个实施例中,多云平台使用符合REST设计风格的RESTfulAPI,直接调用各大SaaS服务系统其封装好的函数/功能的接口,以完成相应的功能。
RESTfulAPI从以下三个方面进行定义:
资源地址:URI,比如:http://CmpAddress/StoreSystem/create_dir
传输的资源:Web服务接受与返回的互联网媒体类型,比如:JSON,XML等。
对资源的操作:Web服务在该资源上所支持的一系列请求方法(比如:POST,GET,PUT或DELETE)。
示例性的,在企业网盘新增一个目录时,请求消息样式和响应消息样式如下:
(1)请求消息样式
POST http://CmpAddress/StoreSystem/create_dir
<Createdir xmlns="http://CmpAddress/StoreSystem/">
<DirName>testCreateDir/</DirName>
<AppAppId>18dca19c5dba42afae4c08d3a970770a</AppAppId>
</Createdir>
(2)响应消息样式
HTTP/1.1 Status:201 Created。
在一个实施例中,还可以将分散在各个第三方服务的用户信息进行整合后储存在多云平台中,通过多云平台同一对用户信息进行管理,指定对用户哪些属性进行何种操作时需要何种审核,统一管理用户的流程,当某位员工离职或调岗时,也可以一次配置就完成所有第三方服务的调整。
上述,本发明实施例提供了一种第三方服务登录方法,当用户登录到多云平台时,多云平台会生成用户的云平台令牌,并且在后续用户调用目标第三方服务时,将云平台令牌作为待校验的第三方服务令牌,对第三方服务令牌进行校验;若校验成功,则目标第三方服务能够在自身系统上完成用户的登录,从而使得用户通过多云平台即可登录到第三方服务上,用户只要一套用户名、密码,即可通访问各大云厂商云资源及企业自身第三方服务系统,而无须再次输入密码,降低用户频繁登陆操作的复杂性;解决了现有技术中用户无法在多云管理平台中对SaaS服务系统和上云应用统一进行登录和管理,导致登录操作复杂且效率低下的技术问题。
实施例二
如图3所示,图3为本发明实施例提供的一种第三方服务登录装置的结构示意图,包括服务注册模块201、令牌生成模块202、校验模块203、用户登录 模块204以及服务调用模块205;
服务注册模块201用于注册第三方服务;
令牌生成模块202用于根据用户的登录请求,登录用户并生成用户的云平台令牌;
校验模块203用于当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌,根据目标第三方服务的验证请求,对第三方服务令牌进行校验;
用户登录模块204用于若校验成功,向目标第三方服务返回认证通过信息,以使目标第三方服务根据认证通过信息,完成用户的登录;
服务调用模块205用于根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能。
在上述实施例的基础上,服务注册模块201用于注册第三方服务具体为:
用于接收第三方服务的接入信息,根据接入信息注册第三方服务,生成第三方服务的标识信息。
在上述实施例的基础上,校验模块203用于当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌具体为:
用于根据用户发送的服务调用指令,以Http调用形式调用目标第三方服务,并将云平台令牌作为待校验的第三方服务令牌,服务调用指令中包含有目标第三方服务的标识信息。
在上述实施例的基础上,校验模块203用于根据目标第三方服务的验证请求,对第三方服务令牌进行校验具体为:
用于根据目标第三方服务的验证请求,判断第三方服务令牌是否为用户的云平台令牌。
在上述实施例的基础上,认证通过信息包括目标第三方服务的标识信息以及预先储存的用户的用户标识信息。
在上述实施例的基础上,用户登录模块204用于以使目标第三方服务根据认证通过信息,完成用户的登录具体为:
用于以使目标第三方服务根据认证通过信息中的标识信息,确定第三方服务令牌通过验证,根据用户标识信息,获取用户的用户信息,根据用户信息创 建并登录用户。
在上述实施例的基础上,服务调用模块205用于根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能具体为:
用于根据用户发送的第三方服务使用指令,调用目标第三方服务的接口,以使目标第三方服务实现相应的功能。
实施例三
本实施例还提供了一种终端设备,如图4所示,一种终端设备30,所述终端设备包括处理器300以及存储器301;
所述存储器301用于存储计算机程序302,并将所述计算机程序302传输给所述处理器;
所述处理器300用于根据所述计算机程序302中的指令执行上述的一种第三方服务登录方法实施例中的步骤。
示例性的,所述计算机程序302可以被分割成一个或多个模块/单元,所述一个或者多个模块/单元被存储在所述存储器301中,并由所述处理器300执行,以完成本申请。所述一个或多个模块/单元可以是能够完成特定功能的一系列计算机程序指令段,该指令段用于描述所述计算机程序302在所述终端设备30中的执行过程。
所述终端设备30可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。所述终端设备30可包括,但不仅限于,处理器300、存储器301。本领域技术人员可以理解,图4仅仅是终端设备30的示例,并不构成对终端设备30的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件,例如所述终端设备30还可以包括输入输出设备、网络接入设备、总线等。
所称处理器300可以是中央处理单元(Central Processing Unit,CPU),还可以是其他通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field-Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器 也可以是任何常规的处理器等。
所述存储器301可以是所述终端设备30的内部存储单元,例如终端设备30的硬盘或内存。所述存储器301也可以是所述终端设备30的外部存储终端设备,例如所述终端设备30上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。进一步地,所述存储器301还可以既包括所述终端设备30的内部存储单元也包括外部存储设备。所述存储器301用于存储所述计算机程序以及所述终端设备30所需的其他程序和数据。所述存储器301还可以用于暂时地存储已经输出或者将要输出的数据。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明 的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储计算机程序的介质。
实施例四
本发明实施例还提供一种包含计算机可执行指令的存储介质,所述计算机可执行指令在由计算机处理器执行时用于执行一种第三方服务登录方法,该方法包括以下步骤:
注册第三方服务;
根据用户的登录请求,登录用户并生成用户的云平台令牌;
当用户调用目标第三方服务时,跳转至目标第三方服务,将云平台令牌作为待校验的第三方服务令牌,根据目标第三方服务的验证请求,对第三方服务令牌进行校验;
若校验成功,向目标第三方服务返回认证通过信息,以使目标第三方服务根据认证通过信息,完成用户的登录;
根据用户发送的第三方服务使用指令,调用目标第三方服务以实现相应的功能。
注意,上述仅为本发明实施例的较佳实施例及所运用技术原理。本领域技术人员会理解,本发明实施例不限于这里所述的特定实施例,对本领域技术人员来说能够进行各种明显的变化、重新调整和替代而不会脱离本发明实施例的保护范围。因此,虽然通过以上实施例对本发明实施例进行了较为详细的说明,但是本发明实施例不仅仅限于以上实施例,在不脱离本发明实施例构思的情况下,还可以包括更多其他等效实施例,而本发明实施例的范围由所附的权利要求范围决定。

Claims (10)

  1. 一种第三方服务登录方法,其特征在于,包括以下步骤:
    注册第三方服务;
    根据用户的登录请求,登录所述用户并生成所述用户的云平台令牌;
    当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌,根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验;
    若校验成功,向所述目标第三方服务返回认证通过信息,以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录;
    根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能。
  2. 根据权利要求1所述的一种第三方服务登录方法,其特征在于,所述注册第三方服务的具体过程为:
    接收第三方服务的接入信息,根据所述接入信息注册所述第三方服务,生成所述第三方服务的标识信息。
  3. 根据权利要求2所述的一种第三方服务登录方法,其特征在于,所述当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌的具体过程为:
    根据所述用户发送的服务调用指令,以Http调用形式调用所述目标第三方服务,并将所述云平台令牌作为待校验的第三方服务令牌,所述服务调用指令中包含有目标第三方服务的标识信息。
  4. 根据权利要求1所述的一种第三方服务登录方法,其特征在于,所述根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验的具体过程为:
    所述根据所述目标第三方服务的验证请求,判断所述第三方服务令牌是否为所述用户的云平台令牌。
  5. 根据权利要求1所述的一种第三方服务登录方法,其特征在于,所述认证通过信息包括所述目标第三方服务的标识信息以及预先储存的所述用户的用户标识信息。
  6. 根据权利要求5所述的一种第三方服务登录方法,其特征在于,所述以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录的具体过程为:
    以使所述目标第三方服务根据所述认证通过信息中的标识信息,确定所述第三方服务令牌通过验证,根据所述用户标识信息,获取所述用户的用户信息,根据所述用户信息创建并登录所述用户。
  7. 根据权利要求1~6任一项所述的一种第三方服务登录方法,其特征在于,所述根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能的具体过程为:
    根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务的接口,以使所述目标第三方服务实现相应的功能。
  8. 一种第三方服务登录装置,其特征在于,包括服务注册模块、令牌生成模块、校验模块、用户登录模块以及服务调用模块;
    所述服务注册模块用于注册第三方服务;
    所述令牌生成模块用于根据用户的登录请求,登录所述用户并生成所述用户的云平台令牌;
    所述校验模块用于当所述用户调用目标第三方服务时,跳转至所述目标第三方服务,将所述云平台令牌作为待校验的第三方服务令牌,根据所述目标第三方服务的验证请求,对所述第三方服务令牌进行校验;
    所述用户登录模块用于若校验成功,向所述目标第三方服务返回认证通过信息,以使所述目标第三方服务根据所述认证通过信息,完成所述用户的登录;
    所述服务调用模块用于根据所述用户发送的第三方服务使用指令,调用所述目标第三方服务以实现相应的功能。
  9. 一种终端设备,其特征在于,所述终端设备包括处理器以及存储器;
    所述存储器用于存储计算机程序,并将所述计算机程序传输给所述处理器;
    所述处理器用于根据所述计算机程序中的指令执行如权利要求1-7中任一项所述的一种第三方服务登录方法。
  10. 一种存储计算机可执行指令的存储介质,其特征在于,所述计算机可执行指令在由计算机处理器执行时用于执行如权利要求1-7中任一项所述的一种第三方服务登录方法。
PCT/CN2021/132684 2021-11-24 2021-11-24 一种第三方服务登录方法、装置、终端设备及存储介质 WO2023092316A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/132684 WO2023092316A1 (zh) 2021-11-24 2021-11-24 一种第三方服务登录方法、装置、终端设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/132684 WO2023092316A1 (zh) 2021-11-24 2021-11-24 一种第三方服务登录方法、装置、终端设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023092316A1 true WO2023092316A1 (zh) 2023-06-01

Family

ID=86538594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/132684 WO2023092316A1 (zh) 2021-11-24 2021-11-24 一种第三方服务登录方法、装置、终端设备及存储介质

Country Status (1)

Country Link
WO (1) WO2023092316A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116886763A (zh) * 2023-09-08 2023-10-13 江苏未来网络集团有限公司 一种通用三方接入平台的对接方法、业务对接方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7500262B1 (en) * 2002-04-29 2009-03-03 Aol Llc Implementing single sign-on across a heterogeneous collection of client/server and web-based applications
CN101651666A (zh) * 2008-08-14 2010-02-17 中兴通讯股份有限公司 一种基于虚拟专用网的身份认证及单点登录的方法和装置
CN105430102A (zh) * 2015-12-28 2016-03-23 东软集团股份有限公司 SaaS网站与第三方系统的集成方法、系统及其装置
CN107786571A (zh) * 2017-11-07 2018-03-09 昆山云景商务服务有限公司 一种用户统一认证的方法
CN109347864A (zh) * 2018-11-22 2019-02-15 杭州迪普科技股份有限公司 基于虚拟专用网络的单点登录方法及装置
CN110069909A (zh) * 2019-04-29 2019-07-30 上海上湖信息技术有限公司 一种免密登录第三方系统的方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7500262B1 (en) * 2002-04-29 2009-03-03 Aol Llc Implementing single sign-on across a heterogeneous collection of client/server and web-based applications
CN101651666A (zh) * 2008-08-14 2010-02-17 中兴通讯股份有限公司 一种基于虚拟专用网的身份认证及单点登录的方法和装置
CN105430102A (zh) * 2015-12-28 2016-03-23 东软集团股份有限公司 SaaS网站与第三方系统的集成方法、系统及其装置
CN107786571A (zh) * 2017-11-07 2018-03-09 昆山云景商务服务有限公司 一种用户统一认证的方法
CN109347864A (zh) * 2018-11-22 2019-02-15 杭州迪普科技股份有限公司 基于虚拟专用网络的单点登录方法及装置
CN110069909A (zh) * 2019-04-29 2019-07-30 上海上湖信息技术有限公司 一种免密登录第三方系统的方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116886763A (zh) * 2023-09-08 2023-10-13 江苏未来网络集团有限公司 一种通用三方接入平台的对接方法、业务对接方法及系统

Similar Documents

Publication Publication Date Title
US20190317757A1 (en) Deployment of infrastructure in pipelines
CN107408064B (zh) 在虚拟机实例内执行命令的方法和用于实施该方法的系统
EP3484125B1 (en) Method and device for scheduling interface of hybrid cloud
CA2825153C (en) Strong rights management for computing application functionality
US9311155B2 (en) System and method for auto-tab completion of context sensitive remote managed objects in a traffic director environment
US8943319B2 (en) Managing security for computer services
CN109844727B (zh) 用于管理应用程序配置和相关联凭证的技术
US10162952B2 (en) Security model for network information service
US11025420B2 (en) Stateless service-mediated security module
US10891569B1 (en) Dynamic task discovery for workflow tasks
US10623410B2 (en) Multi-level, distributed access control between services and applications
US9854031B2 (en) Cloud service agent based on service level agreement(SLA)
US10656939B2 (en) Modeling lifetime of hybrid software application using application manifest
WO2022134186A1 (zh) 区块链的智能合约调用方法、装置、服务器和存储介质
US10547612B2 (en) System to resolve multiple identity crisis in indentity-as-a-service application environment
WO2023165226A1 (zh) 一种应用资源的备份方法、装置、电子设备及存储介质
WO2023092316A1 (zh) 一种第三方服务登录方法、装置、终端设备及存储介质
CN113923023A (zh) 权限配置和数据处理的方法、装置、电子设备及介质
CN114143053A (zh) 一种第三方服务登录方法、装置、终端设备及存储介质
US11195179B2 (en) Detecting cashback and other related reimbursement frauds using blockchain technology
US20190089541A1 (en) Configuration updates for access-restricted hosts
WO2023087278A1 (zh) 一种云平台权限设置方法、装置、终端设备及存储介质
US11526339B1 (en) Systems and methods for improving application installation
US20220086151A1 (en) Peer reviewed access to computing system
CN114331447A (zh) 一种跨链消息提交方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21965054

Country of ref document: EP

Kind code of ref document: A1