WO2022116575A1 - 业务平台的访问权限获取方法和业务平台的访问控制方法 - Google Patents

业务平台的访问权限获取方法和业务平台的访问控制方法 Download PDF

Info

Publication number
WO2022116575A1
WO2022116575A1 PCT/CN2021/109843 CN2021109843W WO2022116575A1 WO 2022116575 A1 WO2022116575 A1 WO 2022116575A1 CN 2021109843 W CN2021109843 W CN 2021109843W WO 2022116575 A1 WO2022116575 A1 WO 2022116575A1
Authority
WO
WIPO (PCT)
Prior art keywords
business platform
platform
service
token
access
Prior art date
Application number
PCT/CN2021/109843
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 亿咖通（湖北）科技有限公司
Publication of WO2022116575A1 publication Critical patent/WO2022116575A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/33—User authentication using certificates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method for obtaining access rights of a business platform, a method, system, electronic device and storage medium for accessing access control of a business platform.
  • Multi-service platform means that different types of services require different external devices to provide support.
  • One service may require overlay access of one application, but as the access layer needs more and more external devices to meet multiple services , there are many shortcomings, such as the inability to flexibly meet the needs of the user, and the user's terminal needs to install multiple client APP applications to support different needs.
  • a user in the field of Internet of Vehicles owns two vehicles, and each vehicle has its own APP to connect to the business platform that provides services for the vehicle, so the user needs to install two APPs.
  • the platform switching method in the prior art is often implemented based on the Oatuh2 protocol.
  • the new business platform requests the user to obtain resources and guides the user to authorize it through the original business platform.
  • the original service platform generates an authentication code bound to the new service platform, and the new service platform can obtain the user's resources and respond to various needs of the user according to the authentication code.
  • This kind of technical solution has the following defects: the original business platform needs to change its functions before it can authorize the new business platform, and at the same time, users need to authorize the new business platform before they can access the new business platform, so that the user's needs cannot be timely To be satisfied, the switching between business platforms cannot be a smooth transition.
  • the embodiments of the present application provide a method for obtaining access rights to a service platform, a method, system, electronic device and storage medium for accessing the service platform, so as to at least solve the problem caused by the need for users to authorize the new service platform before they can access the new service platform.
  • the problem that user needs cannot be met in a timely manner.
  • an embodiment of the present application provides a method for obtaining an access right of a business platform, including: a first business platform obtaining a first access request generated by a client, wherein the first access request is obtained by a user through the client The first login request sent by the terminal is generated, and the first access request carries a second token; the first business platform uses the second token to access the second business platform, and accesses the second business platform from the second token.
  • the second user information in the second account corresponding to the second token is obtained in the business platform; the first business platform generates a first account in the first business platform according to the second user information and generates a the first token corresponding to the first account; the first service platform sends the first token as a response message to the first access request to the client, so that the client can use the The first token obtains the access right of the first business platform.
  • the method before the first service platform obtains the first access request generated by the client, the method further includes: the first service platform obtains, by the first service platform, the first login request sent by the user through the client, wherein , the first login request carries user login information; the first business platform uses the user login information to log in to the second business platform, and obtains the user login information from the second business platform The corresponding second token, wherein the second token is generated in the case of having the second account matching the user login information in the second business platform; the first business platform The second token is sent to the client as a response message to the first login request, so that the client obtains the second token corresponding to the user login information.
  • the logging in the second service platform by the first service platform using the user login information includes: the first service platform generates, according to the first login request, a method for logging in to the second service
  • the second login request of the platform is sent to the second business platform, wherein the second login request carries the user login information.
  • the first business platform uses the second token to access the second business platform, and obtains from the second business platform the account in the second account corresponding to the second token
  • the second user information includes: the first service platform generates a second access request for accessing the second service platform according to the first access request, and sends the second access request to the second service platform, wherein the second access request carries the second token; the first business platform obtains all the information in the second account corresponding to the second token from the second business platform the second user information.
  • the generating, by the first business platform, the first account in the first business platform according to the second user information includes: the first business platform judging whether the first business platform has a first account matching the second user information; in the case that the first business platform does not have a first account matching the second user information, the first business platform will User information creates a first account on the first business platform, and uses the second user information as the first user information in the first account; the first business platform has the same information as the second user information In the case of a matching first account, the first business platform updates the first user information in the first account that matches the second user information according to the second user information.
  • an embodiment of the present application provides an access control method for a service platform, including: the first service platform obtains a third access request sent by a user through a client, wherein the third access request carries service information and a first token, the first token is obtained by the method for obtaining the access right of the business platform according to the first aspect; the first business platform determines, according to the business information, that the third access request is for whether to request the service provided by the first service platform or the second service platform; when the third access request is used to request the service provided by the second service platform, the first service platform will The first token carried in the third access request is replaced with a second token, and a fourth access request is generated and sent to the second service platform; the first service platform obtains the second service platform in response to the The first service request result sent by the fourth access request, and the first service request result is sent to the client as a response message of the third access request.
  • the method further includes: in the case that the third access request is used to request a service provided by the first service platform, the first service platform responds to the third access request A second service request result is generated, and the second service request result is sent to the client as a response message of the third access request.
  • an embodiment of the present application provides an access control system for a business platform, including a first business platform and a second business platform, wherein the first business platform communicates with the second business platform, and the first business platform communicates with the second business platform.
  • a business platform is provided with an interface for client access, and the first business platform is configured to execute the method for obtaining access rights to the business platform according to the first aspect and/or the access to the business platform according to the second aspect. Control Method.
  • an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and running on the processor, where the processor executes the above-mentioned first aspect The method for obtaining the access right of the business platform and/or the method for accessing the business platform according to the second aspect above.
  • an embodiment of the present application provides a storage medium on which a computer program is stored, and when the program is executed by a processor, implements the method for obtaining an access right to a business platform as described in the first aspect above and/or as described above The access control method of the business platform described in the second aspect.
  • the method for obtaining the access authority of the business platform, the access control method for the business platform, the system, the electronic device and the storage medium solve the problem that the user needs to authorize the new business platform before accessing the new business.
  • the problem that the user's needs cannot be met in time caused by the platform allows users to switch business platforms without perception, and realizes the technical effect of flexibly meeting the needs of users.
  • FIG. 1 is a flowchart of a method for obtaining an access right of a business platform according to an embodiment of the present application
  • FIG. 2 is a flowchart of an access control method for a service platform according to an embodiment of the present application
  • FIG. 3 is a structural block diagram of an access control system of a business platform according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.
  • Words like "connected,” “connected,” “coupled,” and the like referred to in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.
  • the “plurality” referred to in this application means greater than or equal to two.
  • “And/or” describes the association relationship between associated objects, indicating that there can be three kinds of relationships. For example, “A and/or B” can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • the terms “first”, “second”, “third”, etc. involved in this application are only to distinguish similar objects, and do not represent a specific order for the objects.
  • the user can perform data transmission with the first service platform through the client based on the HTTP protocol and the MQTT protocol, and the client can be mounted on the mobile device, and can perform data transmission with the second service platform based on the HTTP protocol, wherein , the first service platform can perform data transmission with the second service platform based on the HTTP protocol.
  • the client can be mounted on a mobile terminal, such as an APP application, and the first business platform and the second business platform can also be Based on the HTTP protocol and MQTT protocol, data transmission is performed with the vehicle, and business operations are performed on the vehicle according to the user's needs, such as downloading music and pictures for the vehicle.
  • FIG. 1 is a flowchart of a method for obtaining access rights to a business platform according to an embodiment of the present application. As shown in FIG. 1 , the process includes the following steps:
  • Step S101 the first service platform obtains a first access request generated by the client, wherein the first access request is generated according to the first login request sent by the user through the client, and the first access request carries the second token.
  • the second business platform is registered with multiple second accounts, the second accounts have corresponding second user information, the second accounts are used to uniquely identify users, such as user names and passwords, and each second account corresponds to a second account.
  • User information includes but is not limited to registered mobile phone numbers, avatars, nicknames, etc.
  • both the first service platform and the second service platform may be platforms capable of providing services to users.
  • the interface provided by the platform receives the information and requests sent by the client.
  • the user sends the first access request to the first service platform through the client as an example.
  • the user may be a user of the second business platform, and already has a second account on the second business platform, the second account stores the second user information of the user, and the user inputs the user name and password on the client side
  • the first business platform forwards the first login request to the second business platform
  • the second business platform verifies the user login information in the first login request successfully and generates a second token for accessing the second business platform. Feedback to the first business platform, and the first business platform forwards the second token to the client.
  • the client since the user is a user of the second business platform, after the client obtains the second token, the client generates the first access
  • the request may be obtained from the second service platform through the first access request, and an instruction to obtain user data and perform a service operation may be requested.
  • the first access request may be that the user requests the second service platform for service data such as articles and photos published on the second service platform.
  • the business data corresponding to the first access request is stored in the database of the business platform corresponding to the business data.
  • the first access request carries a second token
  • the second token is the identity verification information used to log in to the second service platform. Therefore, the first access request generated by the client is obtained on the first service platform.
  • An access request wherein before the first access request is generated according to the first login request sent by the user through the client, the client needs to obtain a second token related to the account and password entered by the user, so that the first access request can carry
  • the second token includes the following steps:
  • Step 1 the first business platform obtains the first login request sent by the user through the client, wherein the first login request carries the user login information;
  • Step 2 The first business platform uses the user login information to log in to the second business platform, and obtains a second token corresponding to the user login information from the second business platform, wherein the second token has the same value in the second business platform. Generated when the user login information matches the second account;
  • Step 3 the first service platform sends the second token as a response message to the first login request to the client, so that the client obtains the second token corresponding to the user's login information.
  • the first login request is used to log in to the second service platform, and the user can make the client generate a first login request after entering the account and password on the client.
  • the account and password entered by the client are user login information, which is used for Log in to the second business platform. Since the customer only inputs the account and password for logging in to the second business platform, the first login request is actually received by the first business platform, and the first login request sent by the user through the client is transmitted to the The second business platform, therefore, realizes the packaging of the interface of the second business platform, that is, the client used by the user can still communicate with the second business platform through the agent of the first business platform, and obtain the data and services of the second business platform. .
  • the first service platform may send the second login request to the second service platform through the inter-platform interface.
  • An interface can be a standard for data interaction between two parties (which may be systems, modules, services, etc.).
  • the inter-platform interface may be a standard for data interaction between the first service platform and the second service platform.
  • the first service platform and the second service platform perform wireless or wired data interaction through an inter-platform interface.
  • the purpose of the user is to log in to the second business platform to request data and services provided by the second business platform, so the first login request sent carries the user login used by the user to log in to the second business platform information, where the user login information used to log in to the second business platform is the account number and password entered by the user through the client, and when the user login information meets the login conditions of the second platform, the second platform generates a second token.
  • the first business platform logging in to the second business platform using the user login information includes: the first business platform generates a second login request for logging in to the second business platform according to the first login request, and logs the second login request to the second business platform.
  • the request is sent to the second service platform, wherein the second login request carries user login information.
  • a second login request is generated through the first business platform according to the first login request, wherein the destination address of the second login request is the address of the second business platform, and the source address of the second login request is the first business
  • the address of the platform enables the user to obtain the second token, which is a response message to the first login request, from the second business platform through the first business platform without being aware of it.
  • the client After the first business platform sends the second token to the client as a response message to the first login request, but does not feed back to the user through the client interface or other forms, the client obtains the login permission of the second business platform, and the user can The information of the second business platform is obtained by using the second token, and the data and services provided by the second business platform are accepted.
  • the first business platform and the client can store the second token, and when subsequent users initiate an access request to the second business platform through the client, they can directly pair the second token according to the second token. access to the second business platform.
  • Step S102 the first business platform uses the second token to access the second business platform, and acquires the second user information in the second account corresponding to the second token from the second business platform.
  • the first access request is used to request data in the second business platform, including user data
  • a second token corresponds to a second account in the second business platform
  • the first business platform uses the
  • the second business platform can verify the second token to verify whether the second token is valid.
  • the platform feeds back the second user information in the second account corresponding to the second token; if the second token is invalid, the second user information of the user is not fed back to the first business platform, and the first business platform presets If the second user information of the user is not received within the time period, then send an error message to the client as a response message to the first access request, and prompt the user that the login information such as the user name and password is invalid, or repeat steps 1 and 1. 2.
  • Step 3 obtains the second token again.
  • the first business platform uses the second token to access the second business platform, and obtaining the second user information in the second account corresponding to the second token from the second business platform includes: using the first A transmission protocol between a business platform and a second business platform, the first business platform generates a second access request for accessing the second business platform according to the first access request, and sends the second access request to the second business platform,
  • the second access request carries the second token; the first business platform obtains the second user information in the second account corresponding to the second token from the second business platform, that is, the second business platform receives the first After the second access request, if the second token passes the verification, obtain the second user information in the second account corresponding to the second token and send it to the first business platform.
  • the second account may include user login information for logging in to the second business platform and second user information, wherein the user login information for logging in to the second business platform may include user login information for logging in to the second business platform account and password, the second user information may include but not limited to registered mobile phone number, avatar, nickname, etc.
  • the second access request is generated by the first service platform according to the first access request, mainly that the destination address of the second access request is the address of the second service platform, and the source address of the second access request is the first service
  • the address of the platform can enable the first service platform to request the second user information of the user from the second service platform without the user noticing.
  • Step S103 the first business platform generates a first account and a first token corresponding to the first account in the first business platform according to the second user information.
  • the second user information may also include, but is not limited to, at least one of the following: registered mobile phone number, avatar, nickname, and user name and password when logging in.
  • the second service platform distinguishes user information according to these identifiers.
  • the generating the first account in the first business platform by the first business platform according to the second user information includes: the first business platform determining whether the first business platform has a first account matching the second user information ; Under the situation that there is no first account matching with the second user information in the first business platform, the first business platform creates the first account on the first business platform according to the second user information, and uses the second user information as The first user information in the first account; in the case of a first account matching the second user information in the first business platform, the first business platform updates the first account matching the second user information according to the second user information. The first user information in the account.
  • the first business platform judging whether the first business platform has a first account matching the second user information includes: the first business platform can look up in the first business platform registered user information table whether there is a first account matching the second user information. For the first account related to the user information, for example, through the registered mobile phone number, user name, etc., the registered user information table of the first business platform is queried to detect whether the user has been registered in the first business platform.
  • the user information related to the second user information is not found on the first business platform, it is determined that the user has not registered the first account on the first business platform.
  • the first business platform according to the second user information
  • a new first account is created for the user, that is, the second user information is synchronously entered into the new user account as the first user information, and the first account is obtained. Therefore, the first account and the second user information correspond to The second account has the same user login username and password.
  • the first business platform if user information related to the second user information is found on the first business platform, it is determined that the first business platform has registered a related first account, that is, the first business platform registered user information table In the case of matching the first account related to the second user information, the first business platform updates the preset first business platform registered user information table according to the second user information. Therefore, the first account and the second user information corresponding to the first account.
  • the two accounts have the same user login username and password.
  • the user information related to the first account is the first user information, that is, the user has already registered in the first account.
  • the first business platform can update the corresponding first user information stored in the preset first business platform registered user information table according to the second user information, for example, update the nickname and avatar to It is preset in the first account in the registered user information table of the first business platform.
  • the first user information in the first account corresponds to the second user information in the second account, especially when the user logs in As a user of the second business platform, you can log in to the first business platform by entering the user name and password of the second account on the client terminal, and obtain the services of the first business platform, and the whole process does not require the user to register on the first business platform. and operation.
  • Step S104 the first service platform sends the first token as a response message to the first access request to the client, so that the client obtains the access right of the first service platform by using the first token.
  • the first service platform can store the first token and the second token, and the subsequent access requests sent by the user to the first service platform through the client require services provided by the first service platform or the second service platform.
  • the corresponding business platform can be accessed directly according to the first token or the second token, and the service or information provided by the business platform can be obtained.
  • the platform switching method in the prior art is often implemented based on the Oatuh2 protocol.
  • the new business platform requests the user to obtain resources and guides the user to authorize it through the original business platform.
  • the original service platform generates an authentication code bound to the new service platform, and the new service platform can obtain the user's resources and respond to various needs of the user according to the authentication code.
  • This kind of technical solution has the following defects: the original business platform needs to change its functions before it can authorize the new business platform, and at the same time, users need to authorize the new business platform before they can access the new business platform, so that the user's needs cannot be timely To be satisfied, the switching between business platforms cannot be a smooth transition.
  • this embodiment uses the first service platform to proxy the communication connection between the client used by the user and the second service platform, and obtains the response as the first login request from the second service platform through the first service platform
  • the second token of the message obtains the second user information from the second account in the second business platform through the first business platform, and registers the first account for the user on the first business platform according to the second user information, and then obtains the first account.
  • a token the first business platform controls the access to the first business platform according to the first token, and realizes the switching of business platforms without the user noticing it, and the user can enjoy the services provided by the first business platform at the same time. , you can also enjoy the services provided by the second business platform, complete the integration of the user's account information on the first business platform and the second business platform, and flexibly meet the needs of the user.
  • FIG. 2 is a flowchart of the access control method for a business platform according to an embodiment of the present application. As shown in FIG. 2 , the process includes:
  • Step S201 the first business platform obtains a third access request sent by the user through the client, wherein the third access request carries business information and a first token, and the first token is the access authority of the business platform in the above embodiment get method get.
  • the first business platform may receive a first login request sent by the user through the client, the first business platform generates a first token for accessing the first business platform according to the first login request, and sends the first token to the first business platform.
  • the token is sent to the client as a response message to the first login request.
  • the client obtains the first token, it obtains access rights to the first business platform, and can use the user login information and the first token in the first login request.
  • the first business platform After logging in to the first business platform, the first business platform obtains other business operations of the user from the client again, that is, the third access request performs other business accesses to the first business platform.
  • Step S202 the first service platform determines whether the third access request is for requesting a service provided by the first service platform or the second service platform.
  • Step S203 when the third access request is used to request the service provided by the second service platform, the first service platform replaces the first token carried in the third access request with the second token, and generates a fourth access request Sent to the second business platform.
  • Step S204 the first service platform acquires the first service request result sent by the second service platform in response to the fourth access request, and sends the first service request result to the client as a response message of the third access request.
  • the method further includes: after the first service platform receives the third access request, the third access request carries service information, and judges, according to the service information, that the third access request is for requesting the first service platform It is also a service provided by the second business platform.
  • the third access request is used to request the service provided by the first service platform
  • the first service platform responds to the third access request and uses the first token carried by the first token to access the first service platform, thereby generating the third access request.
  • Second service request result and send the second service request result to the client as a response message of the third access request.
  • the second token is stored by the first service platform, and when the third access request is used to request the service provided by the second service platform, the first token carried in the third access request can be replaced For the second token, use the second token to access the second business platform to obtain services or information provided by the second business platform.
  • the service corresponding to the third access request can be queried in the preset service list to determine which service platform the third access request is to request, and the user requests the first service platform through the client
  • FIG. 3 is a structural block diagram of an access control system of a business platform according to an embodiment of the present application. As shown in FIG. 3 , the system includes:
  • It includes a first business platform 31 and a second business platform 32, wherein the first business platform 31 communicates with the second business platform 32, the first business platform 31 provides an interface accessed by the client 30, and the first business platform 31 is used for executing The method for obtaining access rights of the service platform according to the above-mentioned embodiments and/or the method for accessing control of the service platform according to the above-mentioned embodiments.
  • the first service platform 31 is configured to obtain the first access request generated by the client 30, wherein the first access request is generated according to the first login request sent by the user through the client 30, and the first access request is The access request carries the second token; the first business platform 31 uses the second token to access the second business platform 32, and obtains from the second business platform 32 the second token in the second account corresponding to the second token User information; the first business platform 31 generates a first account and a first token corresponding to the first account in the first business platform 31 according to the second user information; the first business platform 31 uses the first token as the first access A response message of the request is sent to the client 30, so that the client 30 obtains the access right of the first service platform 31 by using the first token.
  • the first business platform 31 is configured to obtain a first login request sent by the user through the client 30, wherein the first login request carries the user login information; the first business platform 31 uses the user The login information logs into the second business platform 32, and obtains a second token corresponding to the user login information from the second business platform 32, wherein the second token has a first token matching the user login information in the second business platform 32. It is generated in the case of two accounts; the first service platform 31 sends the second token to the client 30 as a response message of the first login request, so that the client 30 obtains the second token corresponding to the user's login information.
  • the first business platform 31 is configured to generate a second login request for logging in to the second business platform 32 according to the first login request, and send the second login request to the second business platform 32 , wherein the second login request carries user login information.
  • the first service platform 31 is configured to generate a second access request for accessing the second service platform 32 according to the first access request, and send the second access request to the second service platform 32 , wherein the second access request carries the second token; the first business platform 31 obtains the second user information in the second account corresponding to the second token from the second business platform 32 .
  • the first business platform 31 is configured to determine whether the first business platform 31 has a first account that matches the second user information; the first business platform 31 does not have a first account that matches the second user information; In the case of a first account whose information matches, the first business platform 31 creates a first account on the first business platform 31 according to the second user information, and uses the second user information as the first user information in the first account; When the first business platform 31 has a first account matching the second user information, the first business platform 31 updates the first user information in the first account matching the second user information according to the second user information.
  • the first service platform 31 is configured to obtain a third access request sent by the user through the client 30, wherein the third access request carries service information and a first token, the first token
  • the card is obtained through the access authority acquisition method of the business platform in the above-mentioned embodiment; the first business platform 31 determines whether the third access request is for requesting the service provided by the first business platform 31 or the second business platform 32 according to the business information; When the third access request is used to request the service provided by the second service platform 32, the first service platform 31 replaces the first token carried in the third access request with the second token, generates a fourth access request and sends it to the third access request.
  • the first service platform 31 is configured to generate the first service platform 31 in response to the third access request when the third access request is used to request the service provided by the first service platform 31
  • the second service request result is sent to the client 30 as a response message of the third access request.
  • the user can transmit data with the first service platform 31 through the client 30 based on the HTTP protocol and the MQTT protocol.
  • the client 30 can be mounted on a mobile device, and can communicate with the second service platform 32 based on the HTTP protocol. Data transmission, wherein, the first service platform 31 may perform data transmission with the second service platform 32 based on the HTTP protocol.
  • the client 30 may be mounted on the client, and the first business platform 31 and the second business platform 32 may also be Data transmission is performed with the vehicle 33 based on the HTTP protocol and the MQTT protocol, and business operations are performed on the vehicle 33 according to the user's needs, such as downloading music, pictures, etc. for the vehicle 33 .
  • each of the above modules may be functional modules or program modules, and may be implemented by software or hardware.
  • the above-mentioned modules may be located in the same processor; or the above-mentioned modules may also be located in different processors in any combination.
  • FIG. 4 is a schematic diagram of a hardware structure of the electronic device according to an embodiment of the present application.
  • the electronic device includes: a memory 404 and a processor 402, where a computer program is stored in the memory 404, and the processor 402 is configured to run the computer program to execute the steps in any of the above method embodiments.
  • processor 402 may include a central processing unit (CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC for short), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • memory 404 may include mass storage 404 for data or instructions.
  • the memory 404 may include a Hard Disk Drive (HDD), a floppy disk drive, a Solid State Drive (SSD), flash memory, optical disk, magneto-optical disk, magnetic tape, or universal serial A Universal Serial Bus (USB for short) drive or a combination of two or more of these.
  • Memory 404 may include removable or non-removable (or fixed) media, where appropriate.
  • Memory 404 may be internal or external to the data processing device, where appropriate.
  • memory 404 is a non-volatile (Non-Volatile) memory.
  • the memory 404 includes a read-only memory (Read-Only Memory, referred to as ROM for short) and a random access memory (Random Access Memory, referred to as RAM for short).
  • the ROM can be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, referred to as PROM), an erasable PROM (Erasable Programmable Read-Only Memory, referred to as EPROM), an electrically programmable Erasing PROM (Electrically Erasable Programmable Read-Only Memory, referred to as EEPROM), Electrically Rewritable ROM (Electrically Alterable Read-Only Memory, referred to as EAROM) or Flash (FLASH) or a combination of two or more of these.
  • the RAM may be Static Random-Access Memory (SRAM for short) or Dynamic Random Access Memory (DRAM for short), where DRAM may be a fast page Mode dynamic random access memory 404 (Fast Page Mode Dynamic Random Access Memory, referred to as FPMDRAM), extended data output dynamic random access memory (Extended Date Out Dynamic Random Access Memory, referred to as EDODRAM), synchronous dynamic random access memory ( Synchronous Dynamic Random-Access Memory, referred to as SDRAM) and so on.
  • SRAM Static Random-Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random-Access Memory
  • Memory 404 may be used to store or cache various data files required for processing and/or communication use, and possibly computer program instructions executed by processor 402 .
  • the processor 402 reads and executes the computer program instructions stored in the memory 404 to realize the access control method of any one of the business platforms in the above-mentioned embodiments and/or the acquisition of access rights of any one of the business platforms in the above-mentioned embodiments. method.
  • the aforementioned electronic device may further include a transmission device 406 and an input/output device 408 , wherein the transmission device 406 is connected to the aforementioned processor 402 , and the input/output device 408 is connected to the aforementioned processor 402 .
  • the above-mentioned electronic device is applied to the first service platform, and the above-mentioned processor 402 may be configured to execute the following steps through a computer program:
  • the first service platform obtains a first access request generated by the client, wherein the first access request is generated according to the first login request sent by the user through the client, and the first access request carries the second token.
  • the first business platform uses the second token to access the second business platform, and acquires the second user information in the second account corresponding to the second token from the second business platform.
  • the first business platform generates a first account and a first token corresponding to the first account in the first business platform according to the second user information.
  • the first service platform sends the first token as a response message to the first access request to the client, so that the client obtains the access right of the first service platform by using the first token.
  • the above-mentioned electronic device is applied to the first service platform, and the above-mentioned processor 402 may also be configured to execute the following steps through a computer program:
  • the first service platform obtains a third access request sent by the user through the client, wherein the third access request carries service information and a first token, and the first token passes through the The access permission acquisition method is obtained.
  • the first service platform determines, according to the service information, whether the third access request is for requesting a service provided by the first service platform or the second service platform.
  • the first service platform replaces the first token carried in the third access request with the second token, and generates a fourth access request to send To the second business platform.
  • the first service platform acquires the first service request result sent by the second service platform in response to the fourth access request, and sends the first service request result to the client as a response message of the third access request.
  • the embodiment of the present application may provide a storage medium for implementation.
  • a computer program is stored on the storage medium; when the computer program is executed by the processor, the access control method for any business platform in the above-mentioned embodiments and/or the access rights acquisition method for any business platform in the above-mentioned embodiments is implemented. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Storage Device Security (AREA)

Abstract

本申请涉及一种业务平台的访问权限获取方法、业务平台的访问控制方法、系统、电子装置和存储介质，其中，该访问权限获取方法包括：第一业务平台获取客户端生成的第一访问请求，第一访问请求中携带有第二令牌；第一业务平台利用第二令牌访问第二业务平台，并从第二业务平台中获取与第二令牌对应的第二账户中的第二用户信息；第一业务平台根据第二用户信息在第一业务平台中生成第一账户以及与第一账户对应的第一令牌；第一业务平台将第一令牌作为第一访问请求的响应消息发送给客户端，以使客户端利用第一令牌获得第一业务平台的访问权限。通过本申请，解决了用户需求无法及时得到满足的问题，实现了可以灵活地满足用户的需求的技术效果。

Description

业务平台的访问权限获取方法和业务平台的访问控制方法
本申请要求于2020年12月03日提交中国专利局、申请号为202011397339.1、申请名称为“业务平台的访问权限获取方法和业务平台的访问控制方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别是涉及一种业务平台的访问权限获取方法、业务平台的访问控制方法、系统、电子装置和存储介质。
背景技术
多业务平台是指不同的业务种类需要不同的外部设备提供支持，一个业务可能需要一种应用程序叠加接入，但随着接入层为满足多种业务而需要越来越多的外部设备时，就呈现出很多缺点，如不能灵活地满足用户的需求，用户的终端需要安装多个用于支持不同需求的客户端APP应用。例如车联网领域的用户拥有两辆车，每辆车都有各自的APP连接为车辆提供服务的业务平台，因此用户需要安装两个APP。
总体来说，用户的各类需求，往往在一个业务平台上无法全部满足。为了灵活地满足用户的需求，如何使用户在使用一个客户端的情况下，从不同的业务平台获取服务成为了重要问题。
目前，现有技术中的平台切换方法往往是基于Oatuh2协议实现，新的业务平台向用户请求获取资源并引导用户通过原业务平台对其进行授权，在用户通过对新的业务平台的授权的情况下，原业务平台生成一个与新的业务平台绑定的认证码，新的业务平台可以根据该认证码获取用户的资源并响应用户的各类需求。这类技术方案存在以下缺陷：原业务平台需要对其功能进行改动才可实现对新的业务平台的授权，同时，用户需要先授权给新业务平台才可访问新业务平台，导致用户需求无法及时得到满足，业务平台之间的切换无法平滑过渡。
目前针对相关技术中用户需要先授权给新业务平台才可访问新业务平 台导致的用户需求无法及时得到满足的问题，尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种业务平台的访问权限获取方法、业务平台的访问控制方法、系统、电子装置和存储介质，以至少解决用户需要先授权给新业务平台才可访问新业务平台导致的用户需求无法及时得到满足的问题。
第一方面，本申请实施例提供了一种业务平台的访问权限获取方法，包括：第一业务平台获取客户端生成的第一访问请求，其中，所述第一访问请求根据用户通过所述客户端发送的第一登录请求生成，所述第一访问请求中携带有第二令牌；所述第一业务平台利用所述第二令牌访问所述第二业务平台，并从所述第二业务平台中获取与所述第二令牌对应的第二账户中的第二用户信息；所述第一业务平台根据所述第二用户信息在所述第一业务平台中生成第一账户以及与所述第一账户对应的第一令牌；所述第一业务平台将所述第一令牌作为所述第一访问请求的响应消息发送给所述客户端，以使所述客户端利用所述第一令牌获得所述第一业务平台的访问权限。
在其中一些实施例中，在第一业务平台获取客户端生成的第一访问请求之前，所述方法还包括：所述第一业务平台获取所述用户通过客户端发送的第一登录请求，其中，所述第一登录请求中携带有用户登录信息；所述第一业务平台利用所述用户登录信息登录所述第二业务平台，并从所述第二业务平台中获取与所述用户登录信息对应的所述第二令牌，其中，所述第二令牌在所述第二业务平台中具有与所述用户登录信息匹配的所述第二账户的情况下生成；所述第一业务平台将所述第二令牌作为所述第一登录请求的响应消息发送给所述客户端以使得所述客户端获得与所述用户登录信息对应的所述第二令牌。
在其中一些实施例中，所述第一业务平台利用所述用户登录信息登录所述第二业务平台包括：所述第一业务平台根据所述第一登录请求生成用于登录所述第二业务平台的第二登录请求，并将所述第二登录请求发送给所述第二业务平台，其中，所述第二登录请求中携带有所述用户登录信息。
在其中一些实施例中，所述第一业务平台利用所述第二令牌访问第二 业务平台，并从所述第二业务平台中获取与所述第二令牌对应的第二账户中的第二用户信息包括：所述第一业务平台根据所述第一访问请求生成用于访问所述第二业务平台的第二访问请求，并将所述第二访问请求发送给所述第二业务平台，其中，所述第二访问请求中携带有所述第二令牌；所述第一业务平台从所述第二业务平台中获取与所述第二令牌对应的第二账户中的所述第二用户信息。
在其中一些实施例中，所述第一业务平台根据所述第二用户信息在所述第一业务平台中生成第一账户包括：所述第一业务平台判断所述第一业务平台中是否具有与所述第二用户信息匹配的第一账户；在所述第一业务平台中不具有与所述第二用户信息匹配的第一账户的情况下，所述第一业务平台根据所述第二用户信息在所述第一业务平台上创建第一账户，并将所述第二用户信息作为所述第一账户中的第一用户信息；在所述第一业务平台中具有与第二用户信息匹配的第一账户的情况下，所述第一业务平台根据所述第二用户信息更新与所述第二用户信息匹配的所述第一账户中的第一用户信息。
第二方面，本申请实施例提供了一种业务平台的访问控制方法，包括：第一业务平台获取用户通过客户端发送的第三访问请求，其中，所述第三访问请求中携带有业务信息以及第一令牌，所述第一令牌通过如上述第一方面所述的业务平台的访问权限获取方法获得；所述第一业务平台根据所述业务信息判断所述第三访问请求是用于请求所述第一业务平台还是第二业务平台提供的服务；在所述第三访问请求用于请求所述第二业务平台提供的服务的情况下，所述第一业务平台将所述第三访问请求中携带的所述第一令牌替换为第二令牌，生成第四访问请求发送给所述第二业务平台；所述第一业务平台获取所述第二业务平台响应于所述第四访问请求而发送的第一服务请求结果，并将所述第一服务请求结果作为所述第三访问请求的响应消息发送给所述客户端。
在其中一些实施例中，所述方法还包括：在所述第三访问请求用于请求所述第一业务平台提供的服务的情况下，所述第一业务平台响应于所述第三访问请求而生成第二服务请求结果，并将所述第二服务请求结果作为所述第三访问请求的响应消息发送给所述客户端。
第三方面，本申请实施例提供了一种业务平台的访问控制系统，包括 第一业务平台和第二业务平台，其中，所述第一业务平台与所述第二业务平台通信，所述第一业务平台提供有客户端访问的接口，所述第一业务平台用于执行如上述第一方面所述的业务平台的访问权限获取方法和/或如上述第二方面所述的业务平台的访问控制方法。
第四方面，本申请实施例提供了一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行如上述第一方面所述的业务平台的访问权限获取方法和/或如上述第二方面所述的业务平台的访问控制方法。
第五方面，本申请实施例提供了一种存储介质，其上存储有计算机程序，该程序被处理器执行时实现如上述第一方面所述的业务平台的访问权限获取方法和/或如上述第二方面所述的业务平台的访问控制方法。
相比于相关技术，本申请实施例提供的业务平台的访问权限获取方法、业务平台的访问控制方法、系统、电子装置和存储介质，解决了用户需要先授权给新业务平台才可访问新业务平台导致的用户需求无法及时得到满足的问题，可以让用户在无感知的情况下切换业务平台，实现了可以灵活地满足用户的需求的技术效果。
本申请的一个或多个实施例的细节在以下附图和描述中提出，以使本申请的其他特征、目的和优点更加简明易懂。
附图说明
图1是根据本申请实施例的业务平台的访问权限获取方法的流程图；
图2是根据本申请实施例的业务平台的访问控制方法的流程图；
图3是根据本申请实施例的业务平台的访问控制系统的结构框图；
图4是根据本申请实施例的电子装置的硬件结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行描述和说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。基于本申请提供的实施例，本领域普通技术人员在没有作出创造性劳动的前提下所获得的所有其他实施例， 都属于本申请保护的范围。此外，还可以理解的是，虽然这种开发过程中所作出的努力可能是复杂并且冗长的，然而对于与本申请公开的内容相关的本领域的普通技术人员而言，在本申请揭露的技术内容的基础上进行的一些设计，制造或者生产等变更只是常规的技术手段，不应当理解为本申请公开的内容不充分。
在本申请中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域普通技术人员显式地和隐式地理解的是，本申请所描述的实施例在不冲突的情况下，可以与其它实施例相结合。
除非另作定义，本申请所涉及的技术术语或者科学术语应当为本申请所属技术领域内具有一般技能的人士所理解的通常意义。本申请所涉及的“一”、“一个”、“一种”、“该”等类似词语并不表示数量限制，可表示单数或复数。本申请所涉及的术语“包括”、“包含”、“具有”以及它们任何变形，意图在于覆盖不排他的包含；例如包含了一系列步骤或模块(单元)的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可以还包括没有列出的步骤或单元，或可以还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。本申请所涉及的“连接”、“相连”、“耦接”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电气的连接，不管是直接的还是间接的。本申请所涉及的“多个”是指大于或者等于两个。“和/或”描述关联对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。本申请所涉及的术语“第一”、“第二”、“第三”等仅仅是区别类似的对象，不代表针对对象的特定排序。
在本实施例中，用户可以通过客户端基于HTTP协议、MQTT协议与第一业务平台进行数据传输，客户端可以被搭载于移动设备上，可以基于HTTP协议与第二业务平台进行数据传输，其中，第一业务平台可以基于HTTP协议与第二业务平台进行数据传输。
在本实施例的第一业务平台以及第二业务平台均为车控服务平台的情况下，客户端可以被搭载于移动终端上，例如APP应用程序，第一业务平台以及第二业务平台还可以基于HTTP协议、MQTT协议与车辆进行数据传输， 根据用户的需求对车辆进行业务操作，例如：为车辆下载音乐、图片等。
本实施例提供了一种业务平台的访问控制方法，图1是根据本申请实施例的业务平台的访问权限获取方法的流程图，如图1所示，该流程包括如下步骤：
步骤S101，第一业务平台获取客户端生成的第一访问请求，其中，第一访问请求根据用户通过客户端发送的第一登录请求生成，第一访问请求中携带有第二令牌。
其中，第二业务平台注册有多个第二账户，第二账户中具有对应的第二用户信息，第二账户用于唯一识别用户，例如用户名、密码，每个第二账户对应的第二用户信息包括但不限于注册手机号、头像、昵称等。
在本实施例中，第一业务平台以及第二业务平台均可以是能够向用户提供服务的平台，用户可以通过搭载在移动设备、终端、计算机或者类似的运算装置上的客户端向第一业务平台提供的接口接收客户端发送的信息和请求，下面以用户通过客户端向第一业务平台发送第一访问请求为例。
在本实施例中，用户可以是第二业务平台的用户，在第二业务平台上已经具有第二账户，第二账户存储有该用户的第二用户信息，用户在客户端输入用户名、密码后客户端生成第一登录请求，第一业务平台将第一登录请求转发给第二业务平台，第二业务平台对第一登录请求中的用户登录信息验证成功后生成用于访问第二令牌反馈给第一业务平台，第一业务平台再将第二令牌转发给客户端，此时，由于用户是第二业务平台的用户，客户端获得第二令牌后，客户端生成第一访问请求，可以通过第一访问请求从向第二业务平台请求获取用户数据、进行业务操作的指令。例如，第一访问请求可以是用户向第二业务平台请求在第二业务平台上发布的文章、照片等业务数据。第一访问请求对应的业务数据存储在对应于业务数据的业务平台的数据库中。
在其中一个实施例中，第一访问请求中携带有第二令牌，第二令牌为用于登录第二业务平台的身份验证信息，因此，在第一业务平台获取客户端生成的第一访问请求，其中，第一访问请求根据用户通过客户端发送的第一登录请求生成之前，客户端需要获取与用户输入的账号、密码相关的第二令牌，以使第一访问请求中可以携带该第二令牌，包括如下步骤：
步骤1，第一业务平台获取用户通过客户端发送的第一登录请求，其中，第一登录请求中携带有用户登录信息；
步骤2，第一业务平台利用用户登录信息登录第二业务平台，并从第二业务平台中获取与用户登录信息对应的第二令牌，其中，第二令牌在第二业务平台中具有与用户登录信息匹配的第二账户的情况下生成；
步骤3，第一业务平台将第二令牌作为第一登录请求的响应消息发送给客户端以使得客户端获得与用户登录信息对应的第二令牌。
在本实施例中，第一登录请求用于登录第二业务平台，用户可以在客户端输入账号、密码后使客户端生成第一登录请求，客户输入的账号、密码为用户登录信息，用于登录第二业务平台。由于客户只输入了用于登录第二业务平台的账号和密码，而实际该第一登录请求是由第一业务平台接收，通过第一业务平台将用户通过客户端发送的第一登录请求传递到第二业务平台，因此，实现对第二业务平台接口的包装，即用户使用的客户端通过第一业务平台代理，仍然可以实现与第二业务平台的通信，获取第二业务平台的数据和服务。
其中，第一业务平台可以通过平台间接口，向第二业务平台发送第二登录请求。接口可以是双方(可能是系统、模块、服务等)之间数据交互的一个标准。平台间接口可以为第一业务平台与第二业务平台之间进行数据交互的标准。第一业务平台与第二业务平台通过平台间接口进行无线方式或有线方式的数据交互。
在本实施例中，用户的目的是登录第二业务平台以此请求第二业务平台内的数据和提供的服务，因此发送的第一登录请求携带有用户用于登录第二业务平台的用户登录信息，其中，用于登录第二业务平台的用户登录信息为用户通过客户端输入的账号和密码，当用户登录信息符合第二平台的登录条件时，第二平台生成第二令牌。
在其中一些实施例中，第一业务平台利用用户登录信息登录第二业务平台包括：第一业务平台根据第一登录请求生成用于登录第二业务平台的第二登录请求，并将第二登录请求发送给第二业务平台，其中，第二登录请求中携带有用户登录信息。
在本实施例中，通过第一业务平台根据第一登录请求生成第二登录请求，其中，第二登录请求的目的地址为第二业务平台的地址，第二登录请求的源地址为第一业务平台的地址，使得用户可以在无察觉的情况下，通过第一业务平台从第二业务平台获取作为第一登录请求的响应消息的第二令牌。
第一业务平台将第二令牌作为第一登录请求的响应消息发送给客户端后，但并不通过客户端界面等形式反馈用户，客户端就得到了第二业务平台的登录许可，用户可以利用第二令牌获取第二业务平台的信息同时接受第二业务平台提供的数据和服务。
在本实施例中，第一业务平台和客户端在获得第二令牌后可以存储第二令牌，后续用户通过客户端对第二业务平台发起访问请求时，可以直接根据第二令牌对第二业务平台进行访问。
步骤S102，第一业务平台利用第二令牌访问第二业务平台，并从第二业务平台中获取与第二令牌对应的第二账户中的第二用户信息。
在本实施例中，第一访问请求用于请求第二业务平台内的数据，包括用户数据，一个第二令牌与第二业务平台中的某一第二账户对应，第一业务平台利用第二令牌访问第二业务平台时，第二业务平台可以对第二令牌进行验证，验证第二令牌是否有效，第二业务平台只在第二令牌有效的情况下，向第一业务平台反馈第二令牌对应的第二账户内的第二用户信息；在第二令牌无效的情况下，则不向第一业务平台反馈用户的第二用户信息，第一业务平台在预设时间内未接收到用户的第二用户信息的情况下，则向客户端发送作为第一访问请求的响应消息的报错信息，并提示用户用户名、密码等登录信息无效，或者重复步骤1、步骤2、步骤3再次获取第二令牌。
在其中一个实施例中，第一业务平台利用第二令牌访问第二业务平台，并从第二业务平台中获取与第二令牌对应的第二账户中的第二用户信息包括：利用第一业务平台与第二业务平台之间的传输协议，第一业务平台根据第一访问请求生成用于访问第二业务平台的第二访问请求，并将第二访问请求发送给第二业务平台，其中，第二访问请求中携带有第二令牌；第一业务平台从第二业务平台中获取与第二令牌对应的第二账户中的第二用户信息，即第二业务平台接收到第二访问请求后，在第二令牌通过验证的情况下，获取与第二令牌对应的第二账户中的第二用户信息发送给第一业务平台。
在本实施例中，第二账户可以包括用于登录第二业务平台的用户登录信息和第二用户信息，其中，用于登录第二业务平台的用户登录信息可以包括用于登录第二业务平台的账号和密码，第二用户信息可以包括但不限于注册手机号、头像、昵称等。
在本实施例中，通过第一业务平台根据第一访问请求生成第二访问请求， 主要是第二访问请求的目的地址为第二业务平台的地址，第二访问请求的源地址为第一业务平台的地址，可以在用户在无察觉的情况下，实现第一业务平台向第二业务平台请求用户的第二用户信息。
步骤S103，第一业务平台根据第二用户信息在第一业务平台中生成第一账户以及与第一账户对应的第一令牌。
在本实施例中，第二用户信息还可以包括但不限于以下至少之一：注册手机号、头像、昵称，以及登录时的用户名和密码，第二业务平台根据这些标识区分用户的信息。
在其中一个实施例中，第一业务平台根据第二用户信息在第一业务平台中生成第一账户包括：第一业务平台判断第一业务平台中是否具有与第二用户信息匹配的第一账户；在第一业务平台中不具有与第二用户信息匹配的第一账户的情况下，第一业务平台根据第二用户信息在第一业务平台上创建第一账户，并将第二用户信息作为第一账户中的第一用户信息；在第一业务平台中具有与第二用户信息匹配的第一账户的情况下，第一业务平台根据第二用户信息更新与第二用户信息匹配的第一账户中的第一用户信息。
在本实施例中，第一业务平台判断第一业务平台中是否具有与第二用户信息匹配的第一账户包括：第一业务平台可以在第一业务平台注册用户信息表中查找是否具有与第二用户信息相关的第一账户，例如通过注册手机号、用户名等在第一业务平台注册用户信息表中查询，检测用户是否已经在第一业务平台中注册过。
若在第一业务平台没有查找到与第二用户信息相关的用户信息，则判断用户未在第一业务平台注册第一账户，此时，第一业务平台根据第二用户信息，在第一业务平台注册用户信息表中为用户创建一个新的第一账户，即将第二用户信息作为第一用户信息同步进入新的用户账户，得到第一账户，因此，第一账户和第二用户信息对应的第二账户具有相同的用户登录的用户名和密码。
在其中一个实施例中，若在第一业务平台查找到与第二用户信息相关的用户信息，则判断第一业务平台已经注册有相关的第一账户即在第一业务平台注册用户信息表中匹配到与第二用户信息相关的第一账户的情况下，第一业务平台根据第二用户信息更新预设第一业务平台注册用户信息表，因此，第一账户和第二用户信息对应的第二账户具有相同的用户登录的用户名和密 码。
在本实施例中，在第一业务平台注册用户信息表中匹配与第二用户信息相关的第一账户的情况下，第一账户相关的用户信息为第一用户信息，即用户已在第一业务平台注册第一账户的情况下，第一业务平台可以根据第二用户信息，更新存储在预设第一业务平台注册用户信息表中的对应的第一用户信息，例如把昵称、头像更新到预设第一业务平台注册用户信息表中的第一账户中，因此，针对某一用户，其第一账户中的第一用户信息和第二账户中的第二用户信息对应，尤其是用户登录信息，作为第二业务平台的用户，在客户端输入第二账户的用户名和密码，就可以登录第一业务平台，获得第一业务平台的服务，而整个过程无需用户在第一业务平台进行注册和操作。
步骤S104，第一业务平台将第一令牌作为第一访问请求的响应消息发送给客户端，以使客户端利用第一令牌获得第一业务平台的访问权限。
在本实施例中，第一业务平台可以存储第一令牌、第二令牌，后续用户通过客户端向第一业务平台发送的访问请求需要第一业务平台或第二业务平台提供的服务时，可以直接根据第一令牌或第二令牌对其对应的业务平台进行访问，获取该业务平台提供的服务或信息。
目前，现有技术中的平台切换方法往往是基于Oatuh2协议实现，新的业务平台向用户请求获取资源并引导用户通过原业务平台对其进行授权，在用户通过对新的业务平台的授权的情况下，原业务平台生成一个与新的业务平台绑定的认证码，新的业务平台可以根据该认证码获取用户的资源并响应用户的各类需求。这类技术方案存在以下缺陷：原业务平台需要对其功能进行改动才可实现对新的业务平台的授权，同时，用户需要先授权给新业务平台才可访问新业务平台，导致用户需求无法及时得到满足，业务平台之间的切换无法平滑过渡。
通过上述步骤S101至S104，本实施例通过第一业务平台代理用户使用的客户端与第二业务平台之间的通信连接，通过第一业务平台从第二业务平台获取作为第一登录请求的响应消息的第二令牌，通过第一业务平台从第二业务平台中的第二账户中获取第二用户信息，并根据第二用户信息在第一业务平台为用户注册第一账户，继而获得第一令牌，第一业务平台根据第一令牌进行对第一业务平台的访问控制，在用户无察觉的情况下，实现业务平台的切换，用户可以在享受第一业务平台提供的服务的同时，也可以享受第二业 务平台提供的服务，完成用户在第一业务平台以及第二业务平台的账户信息的整合，可灵活地满足用户的需求。
本实施例提供了一种业务平台的访问控制方法，图2是根据本申请实施例的业务平台的访问控制方法的流程图，如图2所示，该流程包括：
步骤S201，第一业务平台获取用户通过客户端发送的第三访问请求，其中，第三访问请求中携带有业务信息以及第一令牌，第一令牌如上述实施例的业务平台的访问权限获取方法获得。
在本实施例中，第一业务平台可以接收用户通过客户端发送的第一登录请求，第一业务平台根据第一登录请求生成用于访问第一业务平台的第一令牌，并将第一令牌作为第一登录请求的响应消息发送给客户端，客户端获取第一令牌后，即获得第一业务平台的访问权限，可利用第一登录请求中的用户登录信息以及第一令牌登录第一业务平台，之后，第一业务平台再次从客户端获取用户的其他业务操作，即第三访问请求对第一业务平台进行其他业务访问。
步骤S202，第一业务平台判断第三访问请求是用于请求第一业务平台还是第二业务平台提供的服务。
步骤S203，在第三访问请求用于请求第二业务平台提供的服务的情况下，第一业务平台将第三访问请求中携带的第一令牌替换为第二令牌，生成第四访问请求发送给第二业务平台。
步骤S204，第一业务平台获取第二业务平台响应于第四访问请求而发送的第一服务请求结果，并将第一服务请求结果作为第三访问请求的响应消息发送给客户端。
在其中一些实施例中，该方法还包括：第一业务平台在接收到第三访问请求后，第三访问请求携带有业务信息，根据业务信息判断第三访问请求是用于请求第一业务平台还是第二业务平台提供的服务。在第三访问请求用于请求第一业务平台提供的服务的情况下，第一业务平台响应于第三访问请求，利用第一令牌携带的第一令牌访问第一业务平台，从而生成第二服务请求结果，并将第二服务请求结果作为第三访问请求的响应消息发送给客户端。
在本实施例中，通过第一业务平台存储第二令牌，在第三访问请求用于请求第二业务平台提供的服务的情况下，可以将第三访问请求中携带的第一令牌替换为第二令牌，利用第二令牌对第二业务平台进行访问，获取第二业 务平台提供的服务或信息。
在本实施例中，可以通过对第三访问请求对应的服务在预设的服务列表中进行查询，判断第三访问请求用于请求哪种业务平台的服务，用户通过客户端请求第一业务平台的服务时，可以直接通过第一令牌登录成功，而无需注册，在用户无察觉的情况下，实现多业务平台之间的账户整合以及服务整合。
图3是根据本申请实施例的业务平台的访问控制系统的结构框图，如图3所示，该系统包括：
包括第一业务平台31和第二业务平台32，其中，第一业务平台31与第二业务平台32通信，第一业务平台31提供有客户端30访问的接口，第一业务平台31用于执行如上述实施例的业务平台的访问权限获取方法和/或如上述实施例的业务平台的访问控制方法。
在其中一个实施例中，第一业务平台31被配置为用于获取客户端30生成的第一访问请求，其中，第一访问请求根据用户通过客户端30发送的第一登录请求生成，第一访问请求中携带有第二令牌；第一业务平台31利用第二令牌访问第二业务平台32，并从第二业务平台32中获取与第二令牌对应的第二账户中的第二用户信息；第一业务平台31根据第二用户信息在第一业务平台31中生成第一账户以及与第一账户对应的第一令牌；第一业务平台31将第一令牌作为第一访问请求的响应消息发送给客户端30，以使客户端30利用第一令牌获得第一业务平台31的访问权限。
在其中一个实施例中，第一业务平台31被配置为用于获取用户通过客户端30发送的第一登录请求，其中，第一登录请求中携带有用户登录信息；第一业务平台31利用用户登录信息登录第二业务平台32，并从第二业务平台32中获取与用户登录信息对应的第二令牌，其中，第二令牌在第二业务平台32中具有与用户登录信息匹配的第二账户的情况下生成；第一业务平台31将第二令牌作为第一登录请求的响应消息发送给客户端30以使得客户端30获得与用户登录信息对应的第二令牌。
在其中一个实施例中，第一业务平台31被配置为用于根据第一登录请求生成用于登录第二业务平台32的第二登录请求，并将第二登录请求发送给第二业务平台32，其中，第二登录请求中携带有用户登录信息。
在其中一个实施例中，第一业务平台31被配置为用于根据第一访问请求 生成用于访问第二业务平台32的第二访问请求，并将第二访问请求发送给第二业务平台32，其中，第二访问请求中携带有第二令牌；第一业务平台31从第二业务平台32中获取与第二令牌对应的第二账户中的第二用户信息。
在其中一个实施例中，第一业务平台31被配置为用于判断第一业务平台31中是否具有与第二用户信息匹配的第一账户；在第一业务平台31中不具有与第二用户信息匹配的第一账户的情况下，第一业务平台31根据第二用户信息在第一业务平台31上创建第一账户，并将第二用户信息作为第一账户中的第一用户信息；在第一业务平台31中具有与第二用户信息匹配的第一账户的情况下，第一业务平台31根据第二用户信息更新与第二用户信息匹配的第一账户中的第一用户信息。
在其中一个实施例中，第一业务平台31被配置为用于获取用户通过客户端30发送的第三访问请求，其中，第三访问请求中携带有业务信息以及第一令牌，第一令牌通过如上述实施例的业务平台的访问权限获取方法获得；第一业务平台31根据业务信息判断第三访问请求是用于请求第一业务平台31还是第二业务平台32提供的服务；在第三访问请求用于请求第二业务平台32提供的服务的情况下，第一业务平台31将第三访问请求中携带的第一令牌替换为第二令牌，生成第四访问请求发送给第二业务平台32；第一业务平台31获取第二业务平台32响应于第四访问请求而发送的第一服务请求结果，并将第一服务请求结果作为第三访问请求的响应消息发送给客户端30。
在其中一个实施例中，第一业务平台31被配置为用于在第三访问请求用于请求第一业务平台31提供的服务的情况下，第一业务平台31响应于第三访问请求而生成第二服务请求结果，并将第二服务请求结果作为第三访问请求的响应消息发送给客户端30。
在本实施例中，用户可以通过客户端30基于HTTP协议、MQTT协议与第一业务平台31进行数据传输，客户端30可以被搭载于移动设备上，可以基于HTTP协议与第二业务平台32进行数据传输，其中，第一业务平台31可以基于HTTP协议与第二业务平台32进行数据传输。
在本实施例的第一业务平台31以及第二业务平台32均为车控服务平台的情况下，客户端30可以被搭载于客户端上，第一业务平台31以及第二业务平台32还可以基于HTTP协议、MQTT协议与车辆33进行数据传输，根据用户的需求对车辆33进行业务操作，例如：为车辆33下载音乐、图片等。
需要说明的是，上述各个模块可以是功能模块也可以是程序模块，既可以通过软件来实现，也可以通过硬件来实现。对于通过硬件来实现的模块而言，上述各个模块可以位于同一处理器中；或者上述各个模块还可以按照任意组合的形式分别位于不同的处理器中。
本实施例还提供了一种电子装置，图4是根据本申请实施例的电子装置的硬件结构示意图。如图4所示，该电子装置包括：存储器404和处理器402，该存储器404中存储有计算机程序，该处理器402被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
具体地，上述处理器402可以包括中央处理器(CPU)，或者特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
其中，存储器404可以包括用于数据或指令的大容量存储器404。举例来说而非限制，存储器404可包括硬盘驱动器(Hard Disk Drive，简称为HDD)、软盘驱动器、固态驱动器(Solid State Drive，简称为SSD)、闪存、光盘、磁光盘、磁带或通用串行总线(Universal Serial Bus，简称为USB)驱动器或者两个或更多个以上这些的组合。在合适的情况下，存储器404可包括可移除或不可移除(或固定)的介质。在合适的情况下，存储器404可在数据处理装置的内部或外部。在特定实施例中，存储器404是非易失性(Non-Volatile)存储器。在特定实施例中，存储器404包括只读存储器(Read-Only Memory，简称为ROM)和随机存取存储器(Random Access Memory，简称为RAM)。在合适的情况下，该ROM可以是掩模编程的ROM、可编程ROM(Programmable Read-Only Memory，简称为PROM)、可擦除PROM(Erasable Programmable Read-Only Memory，简称为EPROM)、电可擦除PROM(Electrically Erasable Programmable Read-Only Memory，简称为EEPROM)、电可改写ROM(Electrically Alterable Read-Only Memory，简称为EAROM)或闪存(FLASH)或者两个或更多个以上这些的组合。在合适的情况下，该RAM可以是静态随机存取存储器(Static Random-Access Memory，简称为SRAM)或动态随机存取存储器(Dynamic Random Access Memory，简称为DRAM)，其中，DRAM可以是快速页模式动态随机存取存储器404(Fast Page Mode Dynamic Random Access Memory，简称为FPMDRAM)、扩展数据输出动态随机存取存储器(Extended Date Out Dynamic Random Access Memory， 简称为EDODRAM)、同步动态随机存取内存(Synchronous Dynamic Random-Access Memory，简称SDRAM)等。
存储器404可以用来存储或者缓存需要处理和/或通信使用的各种数据文件，以及处理器402所执行的可能的计算机程序指令。
处理器402通过读取并执行存储器404中存储的计算机程序指令，以实现上述实施例中的任意一种业务平台的访问控制方法和/或上述实施例中的任意一种业务平台的访问权限获取方法。
可选地，上述电子装置还可以包括传输设备406以及输入输出设备408，其中，该传输设备406和上述处理器402连接，该输入输出设备408和上述处理器402连接。
可选地，在本实施例中，上述电子装置应用于第一业务平台，上述处理器402可以被设置为通过计算机程序执行以下步骤：
S1，第一业务平台获取客户端生成的第一访问请求，其中第一访问请求根据用户通过客户端发送的第一登录请求生成，第一访问请求中携带有第二令牌。
S2，第一业务平台利用第二令牌访问第二业务平台，并从第二业务平台中获取与第二令牌对应的第二账户中的第二用户信息。
S3，第一业务平台根据第二用户信息在第一业务平台中生成第一账户以及与第一账户对应的第一令牌。
S4，第一业务平台将第一令牌作为第一访问请求的响应消息发送给客户端，以使客户端利用第一令牌获得第一业务平台的访问权限。
可选地，在本实施例中，上述电子装置应用于第一业务平台，上述处理器402还可以被设置为通过计算机程序执行以下步骤：
S1，第一业务平台获取用户通过客户端发送的第三访问请求，其中，第三访问请求中携带有业务信息以及第一令牌，第一令牌通过如上述实施例所述的业务平台的访问权限获取方法获得。
S2，第一业务平台根据业务信息判断第三访问请求是用于请求第一业务平台还是第二业务平台提供的服务。
S3，在第三访问请求用于请求第二业务平台提供的服务的情况下，第一业务平台将第三访问请求中携带的第一令牌替换为第二令牌，生成第四访问请求发送给第二业务平台。
S4，第一业务平台获取第二业务平台响应于第四访问请求而发送的第一服务请求结果，并将第一服务请求结果作为第三访问请求的响应消息发送给客户端。
另外，结合上述实施例中的业务平台的访问控制方法和/或上述实施例中的业务平台的访问权限获取方法，本申请实施例可提供一种存储介质来实现。该存储介质上存储有计算机程序；该计算机程序被处理器执行时实现上述实施例中的任意一种业务平台的访问控制方法和/或上述实施例中的任意一种业务平台的访问权限获取方法。
本领域的技术人员应该明白，以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本申请范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请的保护范围应以所附权利要求为准。

Claims (10)

  1. 一种业务平台的访问权限获取方法，其特征在于，包括：
    第一业务平台获取客户端生成的第一访问请求，其中，所述第一访问请求根据用户通过所述客户端发送的第一登录请求生成，所述第一访问请求中携带有第二令牌；
    所述第一业务平台利用所述第二令牌访问第二业务平台，并从所述第二业务平台中获取与所述第二令牌对应的第二账户中的第二用户信息；
    所述第一业务平台根据所述第二用户信息在所述第一业务平台中生成第一账户以及与所述第一账户对应的第一令牌；
    所述第一业务平台将所述第一令牌作为所述第一访问请求的响应消息发送给所述客户端，以使所述客户端利用所述第一令牌获得所述第一业务平台的访问权限。
  2. 根据权利要求1所述的业务平台的访问权限获取方法，其特征在于，在第一业务平台获取客户端生成的第一访问请求之前，所述方法还包括：
    所述第一业务平台获取所述用户通过客户端发送的第一登录请求，其中，所述第一登录请求中携带有用户登录信息；
    所述第一业务平台利用所述用户登录信息登录所述第二业务平台，并从所述第二业务平台中获取与所述用户登录信息对应的所述第二令牌，其中，所述第二令牌在所述第二业务平台中具有与所述用户登录信息匹配的所述第二账户的情况下生成；
    所述第一业务平台将所述第二令牌作为所述第一登录请求的响应消息发送给所述客户端以使得所述客户端获得与所述用户登录信息对应的所述第二令牌。
  3. 根据权利要求2所述的业务平台的访问权限获取方法，其特征在于，所述第一业务平台利用所述用户登录信息登录所述第二业务平台包括：
    所述第一业务平台根据所述第一登录请求生成用于登录所述第二业务平台的第二登录请求，并将所述第二登录请求发送给所述第二业务平台，其中，所述第二登录请求中携带有所述用户登录信息。
  4. 根据权利要求1所述的业务平台的访问权限获取方法，其特征在于，所述第一业务平台利用所述第二令牌访问第二业务平台，并从所述第二业 务平台中获取与所述第二令牌对应的第二账户中的第二用户信息，包括：
    所述第一业务平台根据所述第一访问请求生成用于访问所述第二业务平台的第二访问请求，并将所述第二访问请求发送给所述第二业务平台，其中，所述第二访问请求中携带有所述第二令牌；
    所述第一业务平台从所述第二业务平台中获取与所述第二令牌对应的第二账户中的所述第二用户信息。
  5. 根据权利要求1所述的业务平台的访问权限获取方法，其特征在于，所述第一业务平台根据所述第二用户信息在所述第一业务平台中生成第一账户包括：
    所述第一业务平台判断所述第一业务平台中是否具有与所述第二用户信息匹配的第一账户；
    在所述第一业务平台中不具有与所述第二用户信息匹配的第一账户的情况下，所述第一业务平台根据所述第二用户信息在所述第一业务平台上创建第一账户，并将所述第二用户信息作为所述第一账户中的第一用户信息；
    在所述第一业务平台中具有与第二用户信息匹配的第一账户的情况下，所述第一业务平台根据所述第二用户信息更新与所述第二用户信息匹配的所述第一账户中的第一用户信息。
  6. 一种业务平台的访问控制方法，其特征在于，所述方法包括：
    第一业务平台获取用户通过客户端发送的第三访问请求，其中，所述第三访问请求中携带有业务信息以及第一令牌，所述第一令牌通过权利要求1至5中任一项所述的业务平台的访问权限获取方法获得；
    所述第一业务平台根据所述业务信息判断所述第三访问请求是用于请求所述第一业务平台还是第二业务平台提供的服务；
    在所述第三访问请求用于请求所述第二业务平台提供的服务的情况下，所述第一业务平台将所述第三访问请求中携带的所述第一令牌替换为第二令牌，生成第四访问请求发送给所述第二业务平台；
    所述第一业务平台获取所述第二业务平台响应于所述第四访问请求而发送的第一服务请求结果，并将所述第一服务请求结果作为所述第三访问请求的响应消息发送给所述客户端。
  7. 根据权利要求6所述的业务平台的访问控制方法，其特征在于，所述方法还包括：
    在所述第三访问请求用于请求所述第一业务平台提供的服务的情况下，所述第一业务平台响应于所述第三访问请求而生成第二服务请求结果，并将所述第二服务请求结果作为所述第三访问请求的响应消息发送给所述客户端。
  8. 一种业务平台的访问控制系统，其特征在于，包括第一业务平台和第二业务平台，其中，所述第一业务平台与所述第二业务平台通信，所述第一业务平台提供有客户端访问的接口，所述第一业务平台用于执行权利要求1至5中任一项所述的业务平台的访问权限获取方法和/或权利要求6至7中任一项所述的业务平台的访问控制方法。
  9. 一种电子装置，包括存储器和处理器，其特征在于，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行权利要求1至5中任一项所述的业务平台的访问权限获取方法和/或权利要求6至7中任一项所述的业务平台的访问控制方法。
  10. 一种存储介质，其特征在于，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行权利要求1至5中任一项所述的业务平台的访问权限获取方法和/或权利要求6至7中任一项所述的业务平台的访问控制方法。
PCT/CN2021/109843 2020-12-03 2021-07-30 业务平台的访问权限获取方法和业务平台的访问控制方法 WO2022116575A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011397339.1 2020-12-03
CN202011397339.1A CN112199656B (zh) 2020-12-03 2020-12-03 业务平台的访问权限获取方法和业务平台的访问控制方法

Publications (1)

Publication Number Publication Date
WO2022116575A1 true WO2022116575A1 (zh) 2022-06-09

Family

ID=74033682

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/109843 WO2022116575A1 (zh) 2020-12-03 2021-07-30 业务平台的访问权限获取方法和业务平台的访问控制方法

Country Status (2)

Country Link
CN (1) CN112199656B (zh)
WO (1) WO2022116575A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115688195A (zh) * 2022-12-15 2023-02-03 深圳市蓝凌软件股份有限公司 区块访问控制方法、鉴权方法、装置、设备和存储介质
CN116992419A (zh) * 2023-09-28 2023-11-03 江西省信息中心(江西省电子政务网络管理中心、江西省信用中心、江西省大数据中心) 地图服务共享权限控制方法、系统、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112199656B (zh) * 2020-12-03 2021-02-26 湖北亿咖通科技有限公司 业务平台的访问权限获取方法和业务平台的访问控制方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101114237A (zh) * 2006-07-25 2008-01-30 因图依特有限公司 转换鉴权令牌以促进应用程序之间的交互的方法和装置
CN102761549A (zh) * 2012-07-03 2012-10-31 中国联合网络通信集团有限公司 资源共享的处理方法和系统以及业务平台
CN110309636A (zh) * 2019-07-04 2019-10-08 阿里巴巴集团控股有限公司 一种身份认证的方法和系统
CN111953708A (zh) * 2020-08-24 2020-11-17 北京金山云网络技术有限公司 基于云平台的跨账号登录方法、装置及服务器
CN112199659A (zh) * 2020-12-03 2021-01-08 湖北亿咖通科技有限公司 用于车辆的多业务平台的访问方法、系统和电子装置
CN112199656A (zh) * 2020-12-03 2021-01-08 湖北亿咖通科技有限公司 业务平台的访问权限获取方法和业务平台的访问控制方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102195957B (zh) * 2010-03-19 2014-03-05 华为技术有限公司 一种资源共享方法、装置及系统
CN104753872B (zh) * 2013-12-30 2018-10-12 中国移动通信集团公司 认证方法、认证平台、业务平台、网元及系统
CN106470190A (zh) * 2015-08-19 2017-03-01 中兴通讯股份有限公司 一种Web实时通信平台鉴权接入方法及装置
US10645079B2 (en) * 2017-05-12 2020-05-05 Bank Of America Corporation Preventing unauthorized access to secured information systems using authentication tokens and multi-device authentication prompts
CN110247901A (zh) * 2019-05-29 2019-09-17 苏宁云计算有限公司 跨平台免密登录访问的方法、系统及设备
CN111694495A (zh) * 2020-06-18 2020-09-22 上海泛微网络科技股份有限公司 一种快速对接第三方app平台的方法、系统和存储介质
CN111709046A (zh) * 2020-06-23 2020-09-25 中国平安财产保险股份有限公司 用户权限数据配置方法、装置、设备及存储介质
CN111933134A (zh) * 2020-07-23 2020-11-13 珠海大横琴科技发展有限公司 人机交互的方法及装置、电子设备、存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101114237A (zh) * 2006-07-25 2008-01-30 因图依特有限公司 转换鉴权令牌以促进应用程序之间的交互的方法和装置
CN102761549A (zh) * 2012-07-03 2012-10-31 中国联合网络通信集团有限公司 资源共享的处理方法和系统以及业务平台
CN110309636A (zh) * 2019-07-04 2019-10-08 阿里巴巴集团控股有限公司 一种身份认证的方法和系统
CN111953708A (zh) * 2020-08-24 2020-11-17 北京金山云网络技术有限公司 基于云平台的跨账号登录方法、装置及服务器
CN112199659A (zh) * 2020-12-03 2021-01-08 湖北亿咖通科技有限公司 用于车辆的多业务平台的访问方法、系统和电子装置
CN112199656A (zh) * 2020-12-03 2021-01-08 湖北亿咖通科技有限公司 业务平台的访问权限获取方法和业务平台的访问控制方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115688195A (zh) * 2022-12-15 2023-02-03 深圳市蓝凌软件股份有限公司 区块访问控制方法、鉴权方法、装置、设备和存储介质
CN116992419A (zh) * 2023-09-28 2023-11-03 江西省信息中心(江西省电子政务网络管理中心、江西省信用中心、江西省大数据中心) 地图服务共享权限控制方法、系统、电子设备及存储介质
CN116992419B (zh) * 2023-09-28 2024-01-02 江西省信息中心(江西省电子政务网络管理中心、江西省信用中心、江西省大数据中心) 地图服务共享权限控制方法、系统、电子设备及存储介质

Also Published As

Publication number Publication date
CN112199656A (zh) 2021-01-08
CN112199656B (zh) 2021-02-26

Similar Documents

Publication Publication Date Title
WO2022116575A1 (zh) 业务平台的访问权限获取方法和业务平台的访问控制方法
US11550759B2 (en) Saving files from third-party systems directly to a cloud storage system
US8474009B2 (en) Dynamic service access
JP6018210B2 (ja) ＯＡｕｔｈフレームワーク
WO2021057889A1 (zh) 一种数据处理方法、装置、电子设备及存储介质
KR102166589B1 (ko) 웹 페이지와 네이티브 애플리케이션 간의 통신을 실현하기 위한 방법 및 장치, 그리고 전자 디바이스
WO2017024791A1 (zh) 一种处理授权的方法和设备
JP2002538525A (ja) ユーザプロファイルデータを用いてクライアントリクエストを増加させるプロキシサーバ
JP7096736B2 (ja) システム、及びデータ処理方法
WO2022116606A1 (zh) 用于车辆的多业务平台的访问方法、系统和电子装置
US20140325089A1 (en) Method, terminal, server and system for page jump
WO2018001023A1 (zh) 一种云终端登录虚拟桌面方法及装置
CN112615810A (zh) 一种访问控制方法及装置
WO2022088710A1 (zh) 一种镜像管理方法及装置
TW201733314A (zh) 執行請求指令的方法及相關的伺服器
US10440100B2 (en) Information processing apparatus, information processing method, and non-transitory computer readable medium
US10341345B1 (en) Network browser configuration
TWI546688B (zh) 對網路位址進行處理的方法及相關的伺服器與非暫態電腦可讀取儲存媒體
WO2015021842A1 (zh) 访问ott应用、服务器推送消息的方法及装置
JP6848275B2 (ja) プログラム、認証システム及び認証連携システム
US20230164135A1 (en) Digital certificate obtaining method and apparatus
TW201824887A (zh) 以認證伺服器在伺服群組中實現免登入之系統及其方法
CN116962020A (zh) 一种通信方法、装置、设备及介质
US20230370447A1 (en) System and method for providing application access through an rdp pool service over a zero trust cloud environment
JP6668861B2 (ja) サービス提供システム、サーバ装置及びプログラム

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: 21899614

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21899614

Country of ref document: EP

Kind code of ref document: A1