WO2017045563A1

WO2017045563A1 - Web app access method, apparatus, and system

Info

Publication number: WO2017045563A1
Application number: PCT/CN2016/098388
Authority: WO
Inventors: 熊亮
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2015-09-17
Filing date: 2016-09-08
Publication date: 2017-03-23
Also published as: CN106549907A; CN106549907B

Abstract

Embodiments of the present application relate to the technical field of cloud computation. Provided are a web app access method, apparatus, and system. The method comprises: acquiring a web page document and an identity authentication token for web app from a first server; loading a web app file in a third server into the web page document; and calling various cloud interfaces of a cloud server by means of the loaded web app file based on the identity authentication token to interact with the cloud server. According to the present application, the degree of coupling of web app is low, and the web app can be flexibly transplanted and reused.

Description

Web app access method, device and system

The present application claims priority to Chinese Patent Application Serial No. No. No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present application relates to the field of cloud computing technologies, and in particular, to a web app access method, apparatus, and system.

Background technique

A web app is an application that is accessed through a network (such as the Internet or an intranet); it can also mean that the computer software is hosted in a browser-supported environment or uses a browser-supported language (such as JavaScript, scripts) and relies on a web browser. Rendered application. The popularity of web apps is due to the popularity of web browsers and the user experience of using this thin and light client. Updates and maintenance can be implemented without having to download and install. It has the intrinsic properties of supporting cross-platform, which is the key reason why web apps are popular. Typical web app products include web mailboxes, web stores, wikis, and more. To implement the web app, the following key conditions must be met:

(1) User interaction. The web app must provide an interface for the user to display data and user operations.

(2) Data interaction. The web app must be able to interact with web services via the Internet using the http protocol, such as data downloads and uploads.

(3) Security guarantee. The web app must have the ability to identify the user's identity and permissions.

Web apps developed by web app developers in the current technology are all developed based on server-local resources. For the first party's web app service provider, it may develop the web app itself, and then deploy the web app on the first party's server for the user to access.

In addition, for the first party, it may not develop the web app by itself, but obtain a third-party developed web app from a third party, for example, the first party copies the complete web app package developed by the third party from the third party. It is then deployed on the first party's own server for user access.

However, in the above several schemes, the user uploads and downloads data through the interface provided by the first party server, and uses the browser's cookie + server session to authenticate in the process, and the web app has high coupling. , can not be transplanted and reused.

Summary of the invention

In view of the above problems, embodiments of the present application have been made in order to provide a web app access method and a corresponding web app access device that overcome the above problems or at least partially solve the above problems.

In order to solve the above problem, the present application discloses a web app access method, including:

Obtaining a webpage document for the web app and an authentication token from the first server;

Loading a web app file in the third server in the webpage document;

Based on the authentication token, the cloud interface of the cloud server is invoked to interact with the cloud server through the loaded web app file.

Also disclosed is a web app access device comprising:

a document and a token obtaining module, configured to obtain a webpage document for the web app and an authentication token from the first server;

a web app file loading module, configured to load a web app file in the third server in the webpage document;

The cloud interaction module is configured to interact with the cloud server by using various cloud interfaces of the cloud server by using the loaded web app file based on the authentication token.

Also disclosed is a web app access system comprising:

Client, first server, third server, cloud server;

The client includes:

Embodiments of the present application include the following advantages:

In the embodiment of the present application, since the webpage document of the first server of the first party is provided, the web app file that is developed by the third party and placed in the third server in the form of static text is provided, and is first by the first party. The server provides an authentication token for the client, so that the client user can click on the related functions of the web app in the webpage of the corresponding webpage document, so that the cloud server can be called with the webapp file after loading. The cloud interface interacts with the cloud server. therefore:

First of all: the web app developed by the third party in the embodiment of the present application is stored in the third file because it can be static file. In the server, the user of the first server of any first party can simply load the web app in the domain name where the first server is located by using the first party webpage document, so that the first party client can use the web app. Full functionality. The web app is highly reusable, and the third party does not need to separately develop a web app for multiple first parties. The first party does not need to build a database and other servers for the web app, thereby reducing the cost of the first party device.

Secondly, when the client uses the web app in its webpage, the client interacts with the cloud server through the authentication token given by the first server, and the client does not need the client cookie+server session authentication method when interacting with the cloud server. To make the web app's coupling low, it can be transplanted and reused flexibly.

DRAWINGS

1 is a flow chart showing the steps of an embodiment of a web app access method of the present application;

2 is a preferred example of step 110 in the embodiment of the web application access method of FIG. 1;

FIG. 3 is a preferred example of the step 120 in the embodiment of the web application access method in FIG. 1;

4 is a preferred example of the step 130 in the embodiment of the web application access method in FIG. 1;

5 is a structural block diagram of an embodiment of a web app access device of the present application;

6 is a structural block diagram of an embodiment of a web app access system of the present application.

detailed description

The above described objects, features and advantages of the present application will become more apparent and understood.

One of the core concepts of the embodiments of the present application is that a third party places a web app file developed by the third party in a third file in the form of a static file, and when the first server constructs a web page document, such as HTML (Hyper text Markup Language) , in the hypertext markup language), the code for loading the web app file is added to the HTML document, so that the client can obtain the HTML document for the web app from the first server and parse through the browser of the client. The HTML document is loaded with the code of the web app file in the HTML document, the web app file is obtained from the third server for loading, and then rendered into the page of the browser, and the first server also assigns the identity verification to the client. The token, so that the client can interact with the cloud server by calling various cloud interfaces of the cloud server through the loaded web app file based on the authentication token. The third-party web app of the embodiment of the present application has low coupling, which increases portability and reusability.

Referring to FIG. 1 , a flow chart of steps of an embodiment of a web app access method of the present application is shown. Including the following steps:

Step 110: Obtain a webpage document for the web app and an authentication token from the first server.

In this embodiment of the present application, the client may access the first server, and obtain an HTML document for the web app from the first server.

At the same time, an authentication token can also be obtained from the first server. For example, for an HTML document whose web application is a web mailbox in the first server, the user can input his identity information, such as a user name and password, in the login page displayed by the browser, and then the user can click on the login in the page, then the client browses. The device can obtain the HTML document corresponding to the web app as a web mailbox from the first server. And receiving an authentication token returned by the first server for the username and password, the authentication token being a token that can be authenticated by the cloud server.

In the embodiment of the present application, the authentication token may use an STS token (Security Token Service token). Of course, other types of authentication tokens may also be used.

In a preferred embodiment of the embodiment of the present application, before step 110, the method further includes:

Step 101: In a primary account corresponding to the first server in the cloud server, allocate a sub-account and generate an original token for the sub-account;

In practical applications, the cloud server can preset a set of account systems, such as RAM (Resource Access Management), and the first-party administrator can apply for a master account in the cloud server, and then in the master account. The sub-accounts of various rights are set below, so that the user of the sub-account can use the sub-account to perform management operations such as corresponding access to the resources of the main account according to their rights.

In the embodiment of the present application, the first account manager applies for a master account in the cloud server by using the account system, and the master account is applied to the first server. The primary account is then assigned a plurality of sub-accounts, and the original token is generated for the sub-account, such as AccessKeyId and AccessKeySecret, that is, the account and password of the sub-account of the login cloud server.

It should be noted that the number of sub-accounts allocated in the primary account may be determined according to the number of client users, for example, according to the number of users registered in the first server using their webabb. It can be understood that the number of sub-accounts is greater than or equal to the number of client users. Preferably, the number of sub accounts is equal to the number of client users

Step 102: The first server corresponds the identity information of the client user to a sub-account, and generates an identity verification token based on the original token.

In order to prevent the client user a from operating the resources of the client user b, the first server of the embodiment of the present application corresponds to one sub-account of one client user, that is, one AccessKeyId and one accessKeySecret correspond to one sub-account.

Then, in order to ensure the security of the original token, the embodiment of the present application generates an identity token based on the original token when the user accesses the foregoing HTML document, such as the foregoing STS token, and the STS token may be one for the client user. Access credentials with custom timeliness and access rights.

For the manual, for the identity information registered by the client user on the first server, such as the username and password, the first server may look up the sub-account of the non-corresponding identity information recorded by the client, and the sub-account corresponds to the newly registered client. The identity information of the user, and then the first server can invoke the STS API of the cloud server for the logged-in client user to generate an authentication token for the identity information of the client user based on the original token.

The STS API, such as AssumeRole, obtains a temporary identity for operating the sub-account through the interface. The AssumeRole includes the following parameters:

1, request parameters:

(1)Action

Type: String

must be

Description: System specified parameters, value: AssumeRole

(2) RoleArn

Type: String

must be

Description: The resource descriptor of the specified role

(3) RoleSessionName

Type: String

must be

Description: Specifies the session name of the temporary identity. This parameter is used to distinguish different temporary identities; it is recommended to use the ID of your external client. Format: ^[a-zA-Z0-9\.@\-_]+$

(4)Policy

Name: Policy

Type: String

Must: no

Description: The specified authorization policy. The default length is limited to 1024 bytes, and the full identity of the temporary identity owned role returned is not specified.

(5) DurationSeconds

Name: DurationSeconds

Type: Integer

Must: no

Description: The specified expiration time in seconds. Expiration time range: 900 to 3600, the default value is 3600.

2, return parameters

(1) Credentials

Type: Credentials

Description: Access credentials

(2) AssumedRoleUser

Type: AssumedRoleUser

Description: Role playing temporary identity

Of course, if all the sub-accounts already have an identity information, you can log in to the cloud server to allocate a sub-account under its main account, generate an AccessKeyId and an AccessKeySecret, and then record the sub-account to the first server. And the identity information of the newly registered client user.

In a preferred embodiment of the embodiment of the present application, referring to FIG. 2, the step 110 includes:

Sub-step 111, sending a webpage request for the web app to the first server; the webpage request includes identity information of the client user;

Sub-step 112, receiving a webpage document for the web app returned by the first server, and receiving an authentication token returned by the first server for the identity information of the client user; wherein the first server is based on the identity of the client Information, obtaining an authentication token corresponding to the identity information.

In the embodiment of the present application, after the first server puts the HTML document for the web app online, it corresponds to a web address, and the client user needs to enable the client to first send a webpage request for the web app, and the identity information is also The request is sent to the first server through the web page.

In an actual application, the webpage request may be a login request. For example, for the webpage that is a webpage for the web app, the client user first needs to open the login page in the client browser, and the login page does not load the webpage of the webmail. file. Then the user can fill in the identity information in the login page, such as the username and password of the client user, such as the username A123 and the password 123456. Then the user clicks login in the login page, then the client sends a login request to the first server. After receiving the login request, the first server verifies whether the username 123 and the password 123456 are correct; if correct, returns to the web app. The HTML code for the web mailbox, and, looking for a sub-account corresponding to the username 123 and the password 123456, generating an STS based on the original token of the sub-account Stoken returns to the client browser.

Step 120: Load a web app file in the third server in the webpage document.

In the application embodiment, the web app files developed by the third party include js (javascript, script) files and CSS (Cascading Style Sheets) files. The two files are respectively stored in the form of static text and a third-party server in the third party, and each file corresponds to a URL link.

For the first party, when developing the HTML document code, it can add the corresponding script and CSS style code in its code according to the W3C (World Wide Web Consortium) standard, which can be the jab of webabb. The link of the file is added to the <script> tag of the HTML code, and the link style of the CSS file is linked in the tag <link>, and the pseudo code is as follows:

In a preferred embodiment of the embodiment of the present application, referring to FIG. 3, the step 120 includes:

Sub-step 121, loading the script file in the third server by using a link of the corresponding script file in the script tag <script> in the webpage document;

Sub-step 122: loading the cascading style sheet file of the third server by a link of the corresponding cascading style sheet file in the style link tag <link> in the webpage document.

In the pseudo code of the foregoing HTML document, after the client browser obtains the HTML document, the DOM (Document Object Model) tree is parsed from the HTML document according to the logic of the browser kernel, and the content in the DOM node is Execution, then for the aforementioned script tag <script>, according to the link in the attribute src in the tag, the js script is obtained from the third server for loading; for the aforementioned style link The link in the attribute "href" in the <link> tag is loaded from the third server to get the css file. Finally, the DOM tree is rendered as a page, and the web app is displayed as a page element in a web page of the first server.

Step 130: Based on the identity verification token, the cloud interface of the cloud server is invoked to interact with the cloud server through the loaded web app file.

As described in step 120, after the client browser loads the web app file in the HTML document, the web app is presented in the web page in the form of a page element. Then, the user can perform various operations such as clicking, input, and the like in the webpage, and the various operations may need to interact with the cloud server to perform functions such as data transmission or downloading.

For example, when the web app is a web mailbox, the page may include an inbox, an outbox, a junk e-mail, a deleted e-mail, a sent e-mail, a write e-mail, etc., for example, by writing an e-mail, the user clicks on the e-mail in the webpage. , in the pop-up interface, the user can enter the recipient's email address in the recipient field, you can enter the subject in the subject field, you can also click the add attachment button, add an attachment, you can click the send button to send, The web mailbox sends a request to the cloud server to call the cloud interface to store the mail under the sub-account corresponding to the username and password. At the same time, the cloud storage interface can be called to send the mail to the mail server.

It can be understood that when the client browser sends a request to the cloud server, it also needs to send the authentication token to the cloud server. The cloud server's account system, such as RAM, verifies that the authentication token is correct. If it is correct, it is allowed to invoke the cloud interface to perform the above operations.

Preferably, referring to FIG. 4, the step 130 includes:

Sub-step 131, initiating an interface call request to the cloud server by using the loaded web app file; the interface call request includes an identity verification token;

In the actual application, the js file and the css file of the web app are loaded, the css file is used to render various buttons of the web app, and the js file is used to implement the logic of each control of the web app, when the user is in the web app area of the page. Inside, click on the various buttons, then js will perform the corresponding operation. For example, if the user clicks to send an email, the logic of the js file initiates an interface call request to the cloud server, and at the same time, the identity STS token can be placed in the interface call request.

Sub-step 132, verifying whether the authentication token is correct;

After receiving the interface call request, the cloud server extracts the identity verification token, and verifies the identity verification token through the local authentication device of the RAM. If the verification is correct, the process proceeds to sub-step 133; if the verification is incorrect , the user is prompted to be wrong.

Sub-step 133, if the authentication verification token is correct, allowing the interface to call the request to call the corresponding The cloud interface interacts.

After the authentication token passes, the request can invoke the corresponding interface of the cloud server to interact with the client. For example, the foregoing email request may call an open storage service interface, such as an OSS (Object Storage Service) to store the mail in the outbox, and also store the mail to the cloud mail server.

In the embodiment of the present application, different web app functions may invoke different cloud interfaces for different interactions. The cloud interface may include:

Open structured data service interfaces, such as Alibaba Cloud's OTS, which is a NoSQL database service built on a distributed system that provides massively structured data storage and real-time access;

Open search service interface, such as OpenSearch, which supports document index structure customization, and free modification, supports automatic docking of cloud storage products, automatic data synchronization update, support for multi-table data push, and field text processing and conversion, such as in web mailboxes. The interface can be called by searching for a message;

Open storage service interfaces, such as OSS (Object Storage Service), users can upload and download data in any application, anytime, anywhere by calling the API, or simply by using the user's web console. Management, OSS is suitable for storing any file type.

Of course, in practical applications, different functions of the web app call different cloud interfaces, and are not limited to the cloud interface described above.

In the embodiment of the present application, since the webpage document of the first server of the first party is provided, the web app file that is developed by the third party and placed in the third server in the form of static text is provided, and is first by the first party. The server provides an authentication token for the client, so that the client user can click on the related functions of the web app in the webpage of the corresponding webpage document, so that the cloud server can be called with the webapp file after loading. The cloud interface interacts with the cloud server.

Therefore, relative to the current technology, the first party web app service provider, which may develop the web app itself, then deploy the web app on the first party's first server, and the first party from the first The third party, copying the complete web app package developed by the third party, and then deploying it on the first party's own third server, the embodiment of the present application has the following advantages:

1. The web app developed by the third party in the embodiment of the present application can be stored in the third server in a static file manner, and the user of the first server of any first party can simply pass the web document of the first party. The web app is loaded in the domain where the server is located, so that the first party's client can use the full functionality of the web app. The web app is highly reusable, and the third party does not need to separately develop a web app for multiple first parties. The first party does not need to build a database and other servers for the web app, thereby reducing the cost of the first party device, and there is no cross. Domain problem.

2. When the client uses the web app in its webpage, the client interacts with the cloud server through the authentication token given by the first server, and the client does not need the client cookie+server session authentication method when interacting with the cloud server. , so that the web app has low coupling degree and can be flexibly transplanted and reused;

3. The first server of the first party can provide an authentication token for the web application of the client, which is equivalent to the web application loaded in the authorized client browser can use the cloud resource corresponding to the first server, which is convenient for the first party. The management and control of privacy by a server is not easily obtained by a third party's third server.

In addition, relative to the third party to develop a complete web app placed on the third server of the third party, the first party provides a service plan for the user by jumping to the third server of the third party, since the first server of the first party is pure It only acts as a springboard, and all of the first-party first servers essentially use the same web app platform for users to access. In this way, the client still uses the browser cookie + server session to authenticate, the coupling is high, and the data from the transmission has cross-domain problems, and the implementation of the present application, for example, the foregoing process, has low coupling and does not exist. Cross-domain problem; Secondly, this method can not transplant the web app platform to each first-party server, so that each first-party server can have its own web app platform, and the web app of the present application can be arbitrarily transplanted to any The first party enables the first server of the first party to have its own web app platform; again, this way the browser cookie + server session is authenticated, and all its files are stored in the third server of the third party. The first server of the first party of the embodiment of the present application can provide an authentication token for the web application of the client, which is equivalent to authorizing the web loaded in the client browser. The app can use the cloud resource corresponding to the first server to facilitate the management and control of the first server of the first party, which is not light. Easy to be acquired by a third party's third server.

It should be noted that, for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the embodiments of the present application are not limited by the described action sequence, because In accordance with embodiments of the present application, certain steps may be performed in other sequences or concurrently. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required in the embodiments of the present application.

Referring to FIG. 5, a structural block diagram of an embodiment of a web app access device of the present application is shown, which may specifically include the following modules:

a document and token obtaining module 510, configured to obtain a webpage document for the web app and an authentication token from the first server;

a web app file loading module 520, configured to load a web app file in the third server in the webpage document;

The cloud interaction module 530 is configured to interact with the cloud server by using various cloud interfaces of the cloud server by using the loaded web app file based on the identity verification token.

In a preferred embodiment of the embodiment of the present application, the document and token obtaining module 510 includes:

a webpage request sending module, configured to send a webpage request for a web app to the first server; the webpage request includes identity information of the client user;

a receiving module, configured to receive a webpage document for the web app returned by the first server, and receive an authentication token returned by the first server for the identity information of the client user; wherein the first server is according to a client Identity information, obtaining an authentication token corresponding to the identity information.

In a preferred embodiment of the embodiment of the present application, before the document and the token obtaining module 510, the method further includes:

Included in the cloud server, an identity allocation module, configured to allocate a sub-account and generate an original token for the sub-account in a primary account of a corresponding first server in the cloud server;

The first server includes: an authentication token generating module, configured to, by the first server, the identity information of the client user is in one-to-one correspondence with a sub-account, and generate an identity verification token based on the original token.

In a preferred embodiment of the embodiment of the present application, the cloud interaction module 530 includes:

An interface call request sending module is configured to initiate an interface call request to the cloud server by using the loaded web app file; the interface call request includes an identity verification token;

An authentication token verification module, configured to verify whether the authentication token is correct;

The calling module is allowed to allow the interface call request to invoke the corresponding cloud interface for interaction if the authentication verification token is correct.

In a preferred embodiment of the embodiment of the present application, the web app file includes:

Web app script files and cascading style sheet files.

In a preferred embodiment of the embodiment of the present application, the web app file loading module 520 includes:

a script file loading module, configured to load the script file in the third server by using a link of a corresponding script file in the script tag <script> in the webpage document;

The cascading style sheet loading module is configured to load the cascading style sheet file of the third server by using a link of the corresponding cascading style sheet file in the style link tag <link> in the webpage document.

In a preferred embodiment of the embodiments of the present application, one or more of an open structured service service interface, an open search service interface, and an open storage service interface are opened.

Referring to FIG. 6, a structural block diagram of an embodiment of a web app access device of the present application is shown, which may specifically include the following modules:

Client 610, first server 620, third server 630, cloud server 640;

The client includes:

a document and token obtaining module 611, configured to obtain a webpage document for the web app and an authentication token from the first server;

a web app file loading module 612, configured to load a web app file in the third server in the webpage document;

The cloud interaction module 613 is configured to interact with the cloud server by using various cloud interfaces of the cloud server by using the loaded web app file based on the identity verification token.

The first server 620 can include a first returning module, which can be used to return a webpage document for the web app and an authentication token according to the webpage request of the server.

The third server 630 can be a second return module, which can be used to return the web app file to the client according to the loading request of the web application of the client.

The cloud server 640 includes an interaction module that can be used to authenticate the client identity and interact with the client.

In a preferred embodiment of the embodiment of the present application, the document and token obtaining module 611 includes:

In a preferred embodiment of the embodiment of the present application, the method further includes:

The cloud server 640 includes: an identity allocation module, configured to allocate a sub-account in the primary account of the corresponding first server in the cloud server, and generate an original token for the sub-account;

The first server 620 includes: an authentication token generating module, configured to, by the first server, the identity information of the client user is in one-to-one correspondence with a sub-account, and generate an identity verification token based on the original token.

In a preferred embodiment of the embodiment of the present application, the cloud interaction module 613 includes:

Web app script files and cascading style sheet files.

In a preferred embodiment of the embodiment of the present application, the web app file loading module 612 includes:

In a preferred embodiment of the embodiment of the present application, the cloud interface includes one or more of an open structured data service interface, an open search service interface, and an open storage service interface.

For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments can be referred to each other.

Those skilled in the art will appreciate that embodiments of the embodiments of the present application can be provided as a method, apparatus, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

In a typical configuration, the computer device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium. Computer readable media includes both permanent and non-persistent, removable and non-removable media. Information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optics Storage, magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by computing devices. As defined herein, computer readable media does not include non-persistent computer readable media, such as modulated data signals and carrier waves.

Embodiments of the present application are described with reference to flowcharts and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device Means are provided for implementing the functions specified in one or more of the flow or in one or more blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The instruction device implements the functions specified in one or more blocks of the flowchart or in a flow or block of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device such that a series of operational steps are performed on the computer or other programmable terminal device to produce computer-implemented processing, such that the computer or other programmable terminal device The instructions executed above provide steps for implementing the functions specified in one or more blocks of the flowchart or in a block or blocks of the flowchart.

While a preferred embodiment of the embodiments of the present application has been described, those skilled in the art can make further changes and modifications to the embodiments once they are aware of the basic inventive concept. Therefore, the appended claims are intended to be interpreted as including all the modifications and the modifications

Finally, it should also be noted that in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities. There is any such actual relationship or order between operations. Furthermore, the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, or terminal device that includes a plurality of elements includes not only those elements but also Other elements that are included, or include elements inherent to such a process, method, article, or terminal device. An element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that comprises the element, without further limitation.

The web app access method, a web app access device and a web app access system provided by the present application are described in detail above. The specific examples are used to explain the principle and implementation manner of the present application. The description of the above embodiments is only for helping to understand the method of the present application and its core ideas; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in specific embodiments and application scopes. In summary, the content of this specification should not be construed as limiting the application.

Claims

A web app access method, comprising:

Obtaining a webpage document for the web app and an authentication token from the first server;

Loading a web app file in the third server in the webpage document;

Based on the authentication token, the cloud interface of the cloud server is invoked to interact with the cloud server through the loaded web app file.
The method according to claim 1, wherein the step of obtaining a webpage document for the web app and an authentication token from the first server comprises:

Sending a webpage request for the web app to the first server; the webpage request includes identity information of the client user;

Receiving a webpage document for the web app returned by the first server, and receiving an identity verification token returned by the first server for the identity information of the client user; wherein the first server obtains and is based on the identity information of the client The identity verification token corresponding to the identity information.
The method according to claim 2, further comprising: before the step of obtaining a webpage document for the web app and the authentication token from the first server, the method further comprising:

Assigning a sub-account and generating an original token for the sub-account in a primary account corresponding to the first server in the cloud server;

The first server corresponds the identity information of the client user to a sub-account and generates an identity verification token based on the original token.
The method according to claim 3, wherein the step of invoking the cloud server to interact with the cloud server by using the loaded web app file based on the identity verification token comprises:

Invoking an interface call request to the cloud server by using the loaded web app file; the interface call request includes an authentication token;

Verify that the authentication token is correct;

If the authentication verification token is correct, the interface call request is allowed to invoke the corresponding cloud interface for interaction.
The method according to any one of claims 1 to 4, wherein the web app file comprises:

Web app script files and cascading style sheet files.
The method according to claim 5, wherein said loading said third service in said webpage document The steps of the web app file in the server include:

Loading the script file in the third server by using a link of the corresponding script file in the script tag <script> in the webpage document;

The cascading style sheet file of the third server is loaded by a link of the corresponding cascading style sheet file in the style link tag <link> in the web page document.
The method of claim 1, wherein the cloud interface comprises one or more of an open structured data service interface, an open search service interface, and an open storage service interface.
A web app access device, comprising:

a document and a token obtaining module, configured to obtain a webpage document for the web app and an authentication token from the first server;

a web app file loading module, configured to load a web app file in the third server in the webpage document;

The cloud interaction module is configured to interact with the cloud server by using various cloud interfaces of the cloud server by using the loaded web app file based on the authentication token.
The device according to claim 8, wherein the document and the token obtaining module comprise:

a webpage request sending module, configured to send a webpage request for a web app to the first server; the webpage request includes identity information of the client user;

a receiving module, configured to receive a webpage document for the web app returned by the first server, and receive an authentication token returned by the first server for the identity information of the client user; wherein the first server is according to a client Identity information, obtaining an authentication token corresponding to the identity information.
The device according to claim 9, further comprising: before the document and the token obtaining module,

Included in the cloud server, an identity allocation module, configured to allocate a sub-account and generate an original token for the sub-account in a primary account of a corresponding first server in the cloud server;

The first server includes: an authentication token generating module, configured to, by the first server, the identity information of the client user is in one-to-one correspondence with a sub-account, and generate an identity verification token based on the original token.
The device according to claim 10, wherein the cloud interaction module comprises:

An interface call request sending module is configured to initiate an interface call request to the cloud server by using the loaded web app file; the interface call request includes an identity verification token;

An authentication token verification module, configured to verify whether the authentication token is correct;

Allowing a calling module to allow the interface to invoke a request if the authentication verification token is correct Interact with the corresponding cloud interface.
The device according to any one of claims 8 to 11, wherein the web app file comprises:

Web app script files and cascading style sheet files.
The device according to claim 12, wherein the web app file loading module comprises:

a script file loading module, configured to load the script file in the third server by using a link of a corresponding script file in the script tag <script> in the webpage document;

The cascading style sheet loading module is configured to load the cascading style sheet file of the third server by using a link of the corresponding cascading style sheet file in the style link tag <link> in the webpage document.
The apparatus according to claim 8, wherein the cloud interface comprises one or more of an open structured data service interface, an open search service interface, and an open storage service interface.
A web app access system, comprising:

Client, first server, third server, cloud server;

The client includes:

a document and a token obtaining module, configured to obtain a webpage document for the web app and an authentication token from the first server;

a web app file loading module, configured to load a web app file in the third server in the webpage document;

The cloud interaction module is configured to interact with the cloud server by using various cloud interfaces of the cloud server by using the loaded web app file based on the authentication token.