CN108134788B - Third party login method and system of cloud operating system - Google Patents
Third party login method and system of cloud operating system Download PDFInfo
- Publication number
- CN108134788B CN108134788B CN201711390928.5A CN201711390928A CN108134788B CN 108134788 B CN108134788 B CN 108134788B CN 201711390928 A CN201711390928 A CN 201711390928A CN 108134788 B CN108134788 B CN 108134788B
- Authority
- CN
- China
- Prior art keywords
- user
- module
- login
- party
- client
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a third party login method and a third party login system of a cloud operating system.A third party login verification module is added in a cloud driving system client, and the third party login verification module is connected with a third party account service; and when the cloud operating system needs to be logged in, logging in the third party account service to log in the cloud operating system. According to the technical scheme provided by the invention, a user can synchronize the setting preference of the operating system, save files to a local storage space, and synchronize all data and preferences on another operating system adopting the method by using the same account.
Description
Technical Field
The invention relates to a cloud operating system login method, in particular to a third party login method and a third party login system of a cloud operating system.
Background
The chrome OS is a cloud operating system that is more in line with the internet era. On the user level, a famous and open-source Google browser is matched with various popular Internet services (SaaS) to provide rich functions for users. The core of the operating system design is to transplant the operation of the traditional operating system which needs to be completed in the local computer to the cloud so as to realize the characteristics of lighter weight, higher speed, higher safety and easier maintenance. The operation of creating, verifying, logging in and the like for the user account is one of the most basic functions of the operating system. As a cloud operating system, the chrome OS accesses the series of functions to the Internet and deeply binds account services provided by Google. When the user starts the operating system for the first time, a new Google account needs to be registered or the existing Google account and a server appointed by Google are used for verification, and the operating system can be continuously used after the verification. If the Google service cannot be accessed for any reason or the Google account is not willing to be used, the operating system cannot be used continuously.
If Google service needs to be abandoned and a Chromium OS operating system is used, the existing technical scheme is to modify a mechanism when the Chromium OS system is activated by a small degree and start a function named as 'visitor mode' in advance. The "guest mode" is by default turned on automatically after system activation. The defect in the united states is that by using the operating system in the "guest mode", all data generated by the user during the use process cannot be stored locally, including but not limited to the user's use preference, downloaded files, accessed websites and the like, and the data can be automatically deleted after the system is powered off. To avoid data loss, great care is taken and the user must log out if they use the system in "guest mode
The cloud backup of the data is done before, and the operation is very troublesome.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a third party login method and a third party login system of a cloud operating system, which overcome the defect that in the prior art, when a user starts the operating system for the first time, a new Google account needs to be registered or the existing Google account and a server specified by Google are used for verification, and the operating system can be continuously used after the verification. If the Google service can not be accessed for any reason or the Google account is not willing to be used, the operating system can not be used continuously.
The purpose of the invention is realized by adopting the following technical scheme:
the invention provides a third party login method of a cloud operating system, and the improvement is that the method comprises the following steps:
adding a third party login verification module in a cloud driving system client, and connecting the third party login verification module with a third party account service;
and when the cloud operating system needs to be logged in, logging in the third party account service to log in the cloud operating system.
Further, adding a third party login verification module in the cloud driving system client, and connecting the third party login verification module with a third party account service includes:
when the cloud driving system client calls a module for processing user login, starting a cloud driving system;
and the module for processing the user login judges whether the cloud driving system is started for the first time or not, and performs corresponding actions on the cloud driving system started for the first time and the non-first-time cloud driving system.
Further, when the cloud driving system is started for the first time, a first start welcome interface is presented to a client user; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet;
and after the user obtains the internet connection, the module for processing the user login presents a new user interface for the client user, and guides the client user to select the third-party account service which the client user wants to use.
Further, when the system is not started for the first time, the module for processing user login judges whether user information logged in before exists in the system, if so, a login interface is presented to the client user, and the logged-in client user is guided to input a login password;
and if not, presenting a presentation to the user to add a new user interface, and guiding the user to select a third-party account service which the user wants to use until the client user completes the creation of a new account.
Further, after the client user inputs a login password, the user management module monitors return information of a third-party account provider to verify the validity of the user account, and if the user is legal, the client user is allowed to log in the system;
the judging the legality of the user account comprises the following steps: the user inputs a password in a page or a module maintained by a third party account provider, and the third party completes the verification of the password; and if the password input by the user accords with the data stored by the third-party account provider, the third-party account provider returns a correct signal to the user management module.
The invention also provides a third party login system of the cloud operating system, and the improvement is that the method comprises the following steps:
the system comprises an adding module, a cloud driving system client and a third party account number service connecting module, wherein the adding module is used for adding a third party login verification module in the cloud driving system client and connecting the third party login verification module with the third party account number service;
and the login module is used for logging in the third party account service to log in the cloud operating system when the cloud operating system needs to be logged in.
Further, the adding module includes:
the client comprises a starting module and a starting module, wherein the starting module is used for starting the cloud driving system when the cloud driving system client calls a module for processing user login;
and the judgment execution sub-module is used for judging whether the cloud driving system is started for the first time by the module for processing the user login and carrying out corresponding actions on the cloud driving system started for the first time and the cloud driving system not started for the first time.
Further, the judgment execution sub-module includes:
the judging unit is used for judging whether the cloud driving system is started for the first time by the module for processing the user login;
and the execution unit is used for carrying out corresponding actions on the first-time starting cloud driving system and the non-first-time starting cloud driving system.
Further, the execution unit includes:
the first execution subunit is used for presenting a first-time starting welcome interface to a client user when the cloud driving system is started for the first time; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet; after the user obtains internet connection, a module for processing user login presents a new user interface for the client user, and guides the client user to select a third-party account service which the client user wants to use;
the second execution subunit is used for judging whether the user information logged in before exists in the system or not by the module for processing the user login when the system is not started for the first time, and if so, presenting a login interface to the client user and guiding the logged-in client user to input a login password;
and if not, presenting a presentation to the user to add a new user interface, and guiding the user to select a third-party account service which the user wants to use until the client user completes the creation of a new account.
The system further comprises a verification unit, a login password input unit and a login control unit, wherein the verification unit is used for monitoring the returned information of a third-party account provider by the user management module to verify the legality of the user account after the login password is input by the client user, and if the returned information is legal, the client user is allowed to log in the system;
the judging the legality of the user account comprises the following steps: the user inputs a password in a page or a module maintained by a third party account provider, and the third party completes the verification of the password; and if the password input by the user accords with the data stored by the third-party account provider, the third-party account provider returns a correct signal to the user management module.
Compared with the closest prior art, the technical scheme provided by the invention has the following beneficial effects:
compared with using the Chromium OS operating system in a 'guest mode', the invention can enable a user to really use the cloud operating system to bring convenience, including but not limited to: the user can synchronize operating system set preferences, save files to local storage space, and use the same account to synchronize all data and preferences on another operating system employing the invention.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a system for first activation or login using a Google account;
FIG. 2 is a schematic diagram of a system for first activation or login using a Google account;
FIG. 3 is a flow chart of login using a third party account service;
FIG. 4 is a schematic diagram of a first activation or login of a system using a third party account in Flint OS;
FIG. 5 is a diagram of a model followed by FAIA communications with third party account services;
fig. 6 is a flowchart of a third party login method of a cloud operating system.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
The first embodiment,
The invention provides a third party login method of a cloud operating system, a flow chart of which is shown in fig. 6, and the method comprises the following steps:
s11, adding a third party login verification module in the cloud driving system client, and connecting the third party login verification module with a third party account service;
and S12, logging in the third party account service to log in the cloud operating system when the cloud operating system needs to be logged in.
Further, adding a third party login verification module in the cloud driving system client, and connecting the third party login verification module with a third party account service includes:
when the cloud driving system client calls a module for processing user login, starting a cloud driving system;
and the module for processing the user login judges whether the cloud driving system is started for the first time or not, and performs corresponding actions on the cloud driving system started for the first time and the non-first-time cloud driving system.
Further, when the cloud driving system is started for the first time, a first start welcome interface is presented to a client user; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet;
and after the user obtains the internet connection, the module for processing the user login presents a new user interface for the client user, and guides the client user to select the third-party account service which the client user wants to use.
Further, when the system is not started for the first time, the module for processing user login judges whether user information logged in before exists in the system, if so, a login interface is presented to the client user, and the logged-in client user is guided to input a login password;
and if not, presenting a presentation to the user to add a new user interface, and guiding the user to select a third-party account service which the user wants to use until the client user completes the creation of a new account.
Furthermore, after the client user inputs a login password, the module for processing the user login calls the user management module to verify the validity of the password, and if the password is legal, the client user is allowed to login the system.
Verifying legitimacy includes: the first determination of whether the password is legitimate is handed over to the third party account provider for execution. Specifically, the user actually completes the entry of the password in a page or module maintained by the third party account provider, and the verification of the password is accomplished purely by the third party. If the password input by the user accords with the data saved by the third party account provider, the third party account provider returns a correct signal to the user management module maintained by the third party. Therefore, the user management module of the my party can judge the legality of the user account only by monitoring the return information of the third party account provider.
The invention also provides a third party login system of the cloud operating system, and the method comprises the following steps:
the system comprises an adding module, a cloud driving system client and a third party account number service connecting module, wherein the adding module is used for adding a third party login verification module in the cloud driving system client and connecting the third party login verification module with the third party account number service;
and the login module is used for logging in the third party account service to log in the cloud operating system when the cloud operating system needs to be logged in.
Further, the adding module includes:
the client comprises a starting module and a starting module, wherein the starting module is used for starting the cloud driving system when the cloud driving system client calls a module for processing user login;
and the judgment execution sub-module is used for judging whether the cloud driving system is started for the first time by the module for processing the user login and carrying out corresponding actions on the cloud driving system started for the first time and the cloud driving system not started for the first time.
Further, the judgment execution sub-module includes:
the judging unit is used for judging whether the cloud driving system is started for the first time by the module for processing the user login;
and the execution unit is used for carrying out corresponding actions on the first-time starting cloud driving system and the non-first-time starting cloud driving system.
Further, the execution unit includes:
the first execution subunit is used for presenting a first-time starting welcome interface to a client user when the cloud driving system is started for the first time; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet; after the user obtains internet connection, a module for processing user login presents a new user interface for the client user, and guides the client user to select a third-party account service which the client user wants to use;
the second execution subunit is used for judging whether the user information logged in before exists in the system or not by the module for processing the user login when the system is not started for the first time, and if so, presenting a login interface to the client user and guiding the logged-in client user to input a login password;
and if not, presenting a presentation to the user to add a new user interface, and guiding the user to select a third-party account service which the user wants to use until the client user completes the creation of a new account.
The system further comprises an authentication unit, wherein the authentication unit is used for calling the user management module to authenticate the password validity by the module for processing the user login after the client user inputs the login password, and if the password is legal, the client user is allowed to log in the system.
The cloud operating system adopts the Google operating system open source code development version.
Example II,
Technical term interpretation:
login: a module for processing user login;
GAIA: a Google account number verification module;
FAIA: a third party account verification module;
UserManager: a user management module;
user: a user object;
AccountId: the user type identifies the object. The user type identification object in the attached drawing has the effects that when the third-party account type login is started, the user is still allowed to login by using a Google account, and the original use experience is kept; the user is also allowed to create a completely local account number which can be used without networking. The system needs to know the user categories that are logged in, such as google account users, WeChat account users, local account users, and so on. The user type identification object is just used for providing identification for identifying the login account category of the user for the operating system.
1. The process of first activating or logging into the system using google account in native chrome OS is shown in fig. 1 below.
2. The principle and design architecture for the first activation or login of a system using the google account in native chrome OS is shown in fig. 2.
The process is described as follows:
the Login process is initiated by a system call Login module when a Chromium OS is started;
judging whether the system is started for the first time by the Login module, and if the system is started for the first time, initiating system information verification to a server specified by Google;
if the system is started for the first time, the Login module presents a welcome interface for the first time starting to the user and guides the user to obtain Internet connection;
after obtaining the internet connection, the Login module further presents a new user interface for the user and guides the user to input the Google account information;
after the user Login information is obtained, the Login module calls the GAIA module, and the GAIA module is responsible for communicating with the cloud Google account service and verifying the validity of the account;
if the account information is legal, the Login module calls a UserManager module, creates a new User object, gives the AccountId as a type identification code of the User, and finally allows the User to log in the system;
if the system is not started for the first time, the Login module judges whether the system has user information logged in before, if so, the Login module presents a Login interface to the user and guides the logged-in user to input a Login password;
after obtaining the user password, the Login module calls a UserManager module to verify the password validity, and if the password is legal, the user is allowed to log in the system
If the system is not started for the first time, the Login module judges whether the user information logged in before exists in the system, if not, the user is presented with a new user adding interface, the user is guided to input Google account information, and the steps are repeated until the user finishes creating a new account
3. In Flint OS, the flow of login using the third party account service is shown in FIG. 3.
4. In Flint OS, the principle and design structure of the system for the first activation or login by using the third-party account is as follows:
the process is described as follows:
the Login process is initiated by a system call Login module when the Flint OS is started
Judging whether the system is started for the first time by the Login module, and if the system is started for the first time, presenting a welcome interface for the first time starting to the user; cutting off the original process of sending machine information with the Google server;
if the system is started for the first time, guiding the user to obtain internet connection;
after obtaining the internet connection, the Login module further presents a new user interface to the user and guides the user to select a third-party account service (such as WeChat, Internet Account, Singleo microblog and the like) which the user wants to use;
after the account number service of the third party appointed by the user is obtained, the Login module calls the FAIA module, and the FAIA module is responsible for verifying the validity of the user information with the appointed account number service of the third party;
if the account information is legal, the Login module calls a UserManager module, creates a new User object, gives the AccountId as a type identification code of the User, and finally allows the User to log in the system;
if the system is not started for the first time, the Login module judges whether the system has user information logged in before, if so, the Login module presents a Login interface to the user and guides the logged-in user to input a Login password;
after obtaining the user password, the Login module calls a UserManager module to verify the password validity, and if the password is legal, the user is allowed to log in the system
If the system is not started for the first time, the Login module judges whether the user information logged in before exists in the system, if not, the Login module presents a presentation to the user to add a new user interface, guides the user to select a third-party account service (such as WeChat, Internet easy account, Xinlang microblog and the like) which the user wants to use, and repeats the steps until the user finishes creating a new account.
5. The communication between the FAIA and the third party account service follows the following model, as shown in fig. 5.
6. The specific technical implementation scheme is as follows:
A. expanding the object: AccountId
Add AccountType: FLINT _ ACCOUNT
B. Expanding the object: user
Add UserType: USER _ TYPE _ FLINT
C. Expanding the object: UserManager
D. Expanding the object: SignIn
Extending the sign _ switches object and adding 'flight-account-support'
E. The extension object, OobeScreen object, adds "SCREEN _ FLINT _ SIGNIN"
F. The FAIA object is created for login and user information update.
The technical scheme provided by the invention ensures that the modified Chromium OS can be more freely and conveniently used in the continental China by stripping the dependence of the original Chromium OS on Google service
According to the technical scheme provided by the invention, the new module (FAIA) is added to serve as a connection controller for the account service of the third party, so that the Chromium OS system can log in the system through the account service of the third party.
According to the technical scheme provided by the invention, the original module is expanded, so that the Chromium OS system can be compatible with the user created through the third-party account and can enjoy the use experience similar to that of the user who uses the Google account to log in the system.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (4)
1. A third party login method of a cloud operating system is characterized by comprising the following steps:
adding a third party login verification module in a cloud driving system client, and connecting the third party login verification module with a third party account service;
when the cloud operating system needs to be logged in, logging in the third party account service to log in the cloud operating system;
the method for adding the third party login verification module in the cloud driving system client and connecting the third party login verification module with the third party account service comprises the following steps:
when the cloud driving system client calls a module for processing user login, starting a cloud driving system;
the method comprises the steps that a module for processing user login judges whether a cloud driving system is started for the first time or not, and corresponding actions are carried out on the cloud driving system which is started for the first time and the cloud driving system which is not started for the first time;
when the cloud driving system is started for the first time, a first start welcome interface is presented to a client user; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet;
after the user obtains internet connection, a module for processing user login presents a new user interface for the client user, and guides the client user to select a third-party account service which the client user wants to use;
when the system is not started for the first time, the module for processing the user login judges whether user information logged in before exists in the system, if so, a login interface is presented to a client user, and the logged-in client user is guided to input a login password;
and if not, presenting a new user interface to the user, and guiding the user to select the third-party account service which the user wants to use until the client user completes the creation of the new account.
2. The third party logging method according to claim 1, wherein after the client user inputs the login password, the user management module monitors the returned information of the third party account provider to verify the validity of the user account, and if the returned information is valid, the client user is allowed to log in the system;
the verifying the validity of the user account comprises the following steps: the user inputs a password in a page or a module maintained by a third party account provider, and the third party completes the verification of the password; and if the password input by the user accords with the data stored by the third-party account provider, the third-party account provider returns a correct signal to the user management module.
3. A third party login system of a cloud operating system, the system comprising:
the system comprises an adding module, a cloud driving system client and a third party account number service connecting module, wherein the adding module is used for adding a third party login verification module in the cloud driving system client and connecting the third party login verification module with the third party account number service;
the login module is used for logging in the cloud operating system by logging in the third party account service when the cloud operating system is required to be logged in;
wherein, the adding module comprises:
the client comprises a starting module and a starting module, wherein the starting module is used for starting the cloud driving system when the cloud driving system client calls a module for processing user login;
the judging and executing submodule is used for judging whether the cloud driving system is started for the first time or not by the module for processing the user login, and carrying out corresponding actions on the cloud driving system which is started for the first time and the cloud driving system which is not started for the first time;
the judgment execution submodule comprises:
the judging unit is used for judging whether the cloud driving system is started for the first time by the module for processing the user login;
the execution unit is used for carrying out corresponding actions on the first-time starting cloud driving system and the non-first-time starting cloud driving system;
the execution unit includes:
the first execution subunit is used for presenting a first-time starting welcome interface to a client user when the cloud driving system is started for the first time; cutting off the original process of sending machine information with the Google server and guiding the client user to connect with the Internet; after the user obtains internet connection, a module for processing user login presents a new user interface for the client user, and guides the client user to select a third-party account service which the client user wants to use;
the second execution subunit is used for judging whether the user information logged in before exists in the system or not by the module for processing the user login when the system is not started for the first time, and if so, presenting a login interface to the client user and guiding the logged-in client user to input a login password;
and if not, presenting a new user interface to the user, and guiding the user to select the third-party account service which the user wants to use until the client user completes the creation of the new account.
4. The third party logging system of claim 3, further comprising a verification unit, configured to, after the client user inputs the login password, monitor a return message of the third party account provider by the user management module to verify the validity of the user account, and if the user account is valid, allow the client user to log in the system;
the verifying the validity of the user account comprises the following steps: the user inputs a password in a page or a module maintained by a third party account provider, and the third party completes the verification of the password; and if the password input by the user accords with the data stored by the third-party account provider, the third-party account provider returns a correct signal to the user management module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711390928.5A CN108134788B (en) | 2017-12-20 | 2017-12-20 | Third party login method and system of cloud operating system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711390928.5A CN108134788B (en) | 2017-12-20 | 2017-12-20 | Third party login method and system of cloud operating system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108134788A CN108134788A (en) | 2018-06-08 |
| CN108134788B true CN108134788B (en) | 2021-02-26 |
Family
ID=62391030
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711390928.5A Active CN108134788B (en) | 2017-12-20 | 2017-12-20 | Third party login method and system of cloud operating system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108134788B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109819020B (en) * | 2019-01-03 | 2021-09-07 | 福建天泉教育科技有限公司 | Third-party platform login and docking method based on configuration and storage medium |
| CN113111328B (en) * | 2021-04-30 | 2022-10-25 | Tcl通讯（宁波）有限公司 | User identity authentication method, system, terminal and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103179164A (en) * | 2011-12-23 | 2013-06-26 | 宇龙计算机通信科技(深圳)有限公司 | Method and communication terminal of storing page information |
| CN103856446A (en) * | 2012-11-30 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Login method and device, and open platform system |
| CN104348777A (en) * | 2013-07-24 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and system for controlling access of mobile terminal to third party server |
| CN104348612A (en) * | 2013-07-23 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Third-party website login method based on mobile terminal and mobile terminal |
| CN105553972A (en) * | 2015-12-14 | 2016-05-04 | 苏州天平先进数字科技有限公司 | Method of using third-party account to log in to screen locking APP community |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530547A (en) * | 2012-07-02 | 2014-01-22 | 爱思爱(天津)高科技有限公司 | Method for logging into third-party application program through integrated authentication function based on Windows operating system |
| CN103686225B (en) * | 2012-08-31 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Remote control method, client side and server side |
| US9432334B2 (en) * | 2014-12-01 | 2016-08-30 | Intermedia.Net, Inc. | Native application single sign-on |
| CN104486318A (en) * | 2014-12-08 | 2015-04-01 | 西安电子科技大学 | Identity authentication method for single sign-on in Android operating system |
| US11386061B2 (en) * | 2015-10-16 | 2022-07-12 | Microsoft Technology Licensing, Llc | Telemetry request system |
-
2017
- 2017-12-20 CN CN201711390928.5A patent/CN108134788B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103179164A (en) * | 2011-12-23 | 2013-06-26 | 宇龙计算机通信科技(深圳)有限公司 | Method and communication terminal of storing page information |
| CN103856446A (en) * | 2012-11-30 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Login method and device, and open platform system |
| CN104348612A (en) * | 2013-07-23 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Third-party website login method based on mobile terminal and mobile terminal |
| CN104348777A (en) * | 2013-07-24 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and system for controlling access of mobile terminal to third party server |
| CN105553972A (en) * | 2015-12-14 | 2016-05-04 | 苏州天平先进数字科技有限公司 | Method of using third-party account to log in to screen locking APP community |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108134788A (en) | 2018-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10075426B2 (en) | Web-based single sign-on with form-fill proxy application | |
| CN110612528B (en) | Method, system and computer storage medium for securely authenticating an automated program user | |
| US10069832B2 (en) | Ephemeral applications | |
| CN104025539B (en) | The method and apparatus for promoting single-sign-on services | |
| CN103036902B (en) | Log-in control method and system based on Quick Response Code | |
| CN104079409A (en) | Account login method and device | |
| US8656473B2 (en) | Linking web identity and access to devices | |
| US9389873B2 (en) | Kiosk application mode for operating system | |
| US20180227296A1 (en) | Authentication on thin clients using independent devices | |
| US9807609B2 (en) | Multiple profiles on a shared computing device | |
| US11257042B2 (en) | Workflow service email integration | |
| TW201828162A (en) | Device configuration method, apparatus and system | |
| CN108134788B (en) | Third party login method and system of cloud operating system | |
| CN111523102A (en) | Applet login method, device, equipment and computer readable storage medium | |
| US11722476B2 (en) | Workflow service back end integration | |
| CN111078424A (en) | Information interaction method and device, computer equipment and storage medium | |
| CN111191200A (en) | Page display method and device and electronic equipment | |
| US11265309B2 (en) | Workflow service back end integration | |
| CN106209746B (en) | Security service providing method and server | |
| WO2016112792A1 (en) | Identity authentication method and device | |
| CN103248635A (en) | Contact processing method, terminal and server | |
| CN104079536A (en) | Mobile reading client and method of logging in to server from client | |
| CN113905263B (en) | Set top box control method, equipment and storage medium | |
| US20220174057A1 (en) | Workflow service back end integration | |
| CN114357430A (en) | Remote log-out method and system based on third party authentication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |