CN105516163A - Login method, terminal device and communication system - Google Patents
Login method, terminal device and communication system Download PDFInfo
- Publication number
- CN105516163A CN105516163A CN201510966911.4A CN201510966911A CN105516163A CN 105516163 A CN105516163 A CN 105516163A CN 201510966911 A CN201510966911 A CN 201510966911A CN 105516163 A CN105516163 A CN 105516163A
- Authority
- CN
- China
- Prior art keywords
- server
- client
- authentication
- logging
- software
- 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.)
- Granted
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a login method, a terminal device and a communication system. The method comprises that: a software client builds long connection with a software server and applies for safe starting parameters; the software client applies to a system server for a temporary certificate through a system client, wherein the application comprises the safe starting parameters; the system server generates the temporary certificate; after receiving the temporary certificate, the software server searches a first database to obtain a first safe starting parameter according to the connection information of the long connection and sends the temporary certificate and the first safe starting parameter to the system server; the system server searches a second database according to the first safe starting parameter so as to obtain a second safe starting parameter and a login certificate and returns the login certificate when the two parameters are in accord; the software server sends the login certificate to an account server for verification and accepts login of the software client after the verification is successful.
Description
Technical field
The present invention relates to communication technical field, particularly relate to a kind of login method terminal equipment and communication system.
Background technology
Along with the development of development of Mobile Internet technology, various software may be had to apply under an Internet firm, all software application share same set of account system.But user often logs in application software application all needs to input respectively a corresponding user cipher, and input operation number of times is too much, and flow process is too loaded down with trivial details, and user-interaction experience is poor.
At present, partial software application provides the memory function of user name password, and user is when first time logs in after input username and password, and log-on message can be kept at this locality by software application, and user just need not input username and password again subsequently.In addition, some website is as Sina, Tengxun, third party's login feature is provided for solving Similar Problems, by readjustment url (URL(uniform resource locator), UniformResourceLocator, be called for short url) and relevant parameter transmit its log-on message, make user on other websites, the account of Sina or Tengxun also can be used to log in.
Summary of the invention
Inventor in the practice of the invention, find that above-mentioned existing login method exists following shortcoming: log-on message is kept at local method and is easily stolen by Malware application, thus cause accounts information to be illegally used, reduce the fail safe of accounts information.And depend on browser by the method that readjustment url and relevant parameter transmit its log-on message, non-website scenario cannot be applied to.Visible, the login method of existing same account system makes user's complex operation, account security lower.
In order to overcome the shortcoming that prior art exists, the embodiment of the present invention provides a kind of login method and terminal equipment and communication system, for user provides safe Auto Login feature, strengthens Consumer's Experience, ensure that fail safe.
First aspect, the embodiment of the present invention provides a kind of login method, comprising:
Software client and system client set up local interface channel, and receive by described local interface channel the accounts information that described system client provides; Wherein, described software client and described system client are configured in same terminal equipment, and described system client has used described accounts information to be successfully logged onto system server, stores the logging on authentication corresponding with described accounts information in described system server;
Described software client sends logging request to software server, sets up long interface channel with described software server; Wherein, described logging request comprises described accounts information;
Described software client receives the clean boot parameter of described software server transmission by described long interface channel; Wherein, in described software server, be configured with the first database, for storing the related information of the link information three of described clean boot parameter, described accounts information and described long interface channel;
Described software client sends scrip application request to described system client; Wherein, described scrip application request comprises described clean boot parameter;
Described scrip application request forward is given described system server by described system client, to ask described system server to generate scrip, and described scrip is returned to described system client; Wherein, in described system server, be configured with the second database, for storing the related information of described scrip, described clean boot parameter and described logging on authentication three;
Described software client receives the described scrip that described system client forwards, and by described long interface channel, described scrip is sent to described software server, to make described software server according to the link information of described long interface channel, inquire about described first database, obtain the first clean boot parameter, and send logging on authentication application request to described system server; Wherein, described logging on authentication application request comprises described first clean boot parameter and described scrip, thus make described system server according to described second database of described scrip inquiry, obtain the second clean boot parameter, and when confirming described first clean boot parameter and described second clean boot parameter is consistent, logging on authentication associated by described scrip is sent to described software server, uses the logging on authentication of described association to account server request login authentication to enable described software server;
Described software client, after the logging on authentication of described association passes through certification, uses described accounts information to sign in described software server.
Further, described software client and system client set up local interface channel, and receive by described local interface channel the accounts information that described system client provides, and specifically comprise:
Described software client receives the link information of the local interface channel that described system client sends;
Described software client, according to the link information of described local interface channel, sends handshake authentication information to described system client, carries out handshake authentication to ask described system client;
Described software client after legal by described system client certification, sets up described local interface channel with described system client, and receives by described local interface channel the accounts information that described system client provides.
Further, described local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.
Further, before described software client and system client set up local interface channel, also comprise:
Described accounts information is sent to account server by described system client, to ask described account server to verify described accounts information, and generates the logging on authentication corresponding with described accounts information after being proved to be successful;
Described system client receives described logging on authentication, and is saved in internal memory;
Described logging on authentication is transmitted to described system server by described system client, to make described system server to the legitimacy of logging on authentication described in described account server requests verification, and after described logging on authentication is verified, stores described logging on authentication;
Described system client receives after logging on authentication that described system server returns verifies legal information, deletes described logging on authentication, and use described accounts information to sign in described system server from internal memory.
Further, use after described accounts information signs in described system server at described system client, also comprise:
Described system client also receives the log-on message that described system server sends, and uses the hardware characteristics information of native system client be encrypted described log-on message and store;
When described system client needs to carry out automatic login authentication, described log-on message is sent to described system server, to make described system server after the described log-on message of checking is legal, accept described system client and use described user account automatically to log in.
Further, described clean boot parameter increases variable by described software server certainly according to one of the mark of this software server and this software server, generates according to the create-rule preset.
Further, described scrip is 32 readable random strings, and within effective time only can certification once;
Wherein, the connect hours of described long interface channel is shorter than described effective time.
Second aspect, embodiments provides a kind of terminal equipment, is configured with software client and system client in described terminal equipment;
Described software client comprises:
Local connecting construction unit, for setting up local interface channel with described system client, and receiving by described local interface channel the accounts information that described system client provides; Wherein, described system client has used described accounts information to be successfully logged onto system server, stores the logging on authentication corresponding with described accounts information in described system server;
Long connection construction unit, for sending logging request to software server, sets up long interface channel with described software server; Wherein, described logging request comprises described accounts information;
First receiving element, for receiving the clean boot parameter that described software server sends by described long interface channel; Wherein, in described software server, be configured with the first database, for storing the related information of the link information three of described clean boot parameter, described accounts information and described long interface channel;
With, the first transmitting element, for sending scrip application request to described system client; Wherein, described scrip application request comprises described clean boot parameter;
Described system client comprises: the second transmitting element;
Described second transmitting element is used for by described scrip application request forward to described system server, to ask described system server to generate scrip, and described scrip is returned to described system client; Wherein, in described system server, be configured with the second database, for storing the related information of described scrip, described clean boot parameter and described logging on authentication three;
Described software client also comprises:
Second receiving element, for receiving the described scrip that described system client forwards, and by described long interface channel, described scrip is sent to described software server, to make described software server according to the link information of described long interface channel, inquire about described first database, obtain the first clean boot parameter, and send logging on authentication application request to described system server; Wherein, described logging on authentication application request comprises described first clean boot parameter and described scrip, thus make described system server according to described second database of described scrip inquiry, obtain the second clean boot parameter, and when confirming described first clean boot parameter and described second clean boot parameter is consistent, logging on authentication associated by described scrip is sent to described software server, uses the logging on authentication of described association to account server request login authentication to enable described software server;
With, first logs in unit, for the logging on authentication in described association by after certification, uses described accounts information to sign in described software server.
Further, described this locality connection construction unit comprises:
First receives subelement, for receiving the link information of the local interface channel that described system client sends;
First sends subelement, for the link information according to described local interface channel, sends handshake authentication information, carry out handshake authentication to ask described system client to described system client;
With, local connection builds subelement, for after legal by described system client certification, sets up described local interface channel with described system client, and receives by described local interface channel the accounts information that described system client provides.
Further, described local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.
Further, described system client also comprises:
3rd transmitting element, before setting up at described local interface channel, described accounts information is sent to account server, to ask described account server to verify described accounts information, and generates the logging on authentication corresponding with described accounts information after being proved to be successful;
3rd receiving element, for receiving described logging on authentication, and is saved in internal memory;
4th transmitting element, for described logging on authentication is transmitted to described system server, to make described system server to the legitimacy of logging on authentication described in described account server requests verification, and after described logging on authentication is verified, store described logging on authentication;
With, second logs in unit, after the logging on authentication returned verifies legal information, deletes described logging on authentication from internal memory, and use described accounts information to sign in described system server for receiving described system server.
Further, described system client also comprises:
4th receiving element, use after described accounts information signs in described system server for logging in unit described second, receive the log-on message that described system server sends, and use the hardware characteristics information of native system client be encrypted described log-on message and store;
With, 3rd logs in unit, for when needs carry out automatic login authentication, described log-on message is sent to described system server, to make described system server after the described log-on message of checking is legal, accept described system client and use described user account automatically to log in.
Further, described clean boot parameter increases variable by described software server certainly according to one of the mark of this software server and this software server, generates according to the create-rule preset.
Further, described scrip is 32 readable random strings, and within effective time only can certification once;
Wherein, the connect hours of described long interface channel is shorter than described effective time.
The third aspect, embodiments provides a kind of communication system, comprises account server, system server, software server and the terminal equipment as described in any one of second aspect.
Visible, implement the embodiment of the present invention, there is following beneficial effect:
The login method that the embodiment of the present invention provides and terminal equipment and communication system, after the system client information of accessing to your account is successfully logged onto system device, software client and system client set up local interface channel, obtain account information and also start login process.Software client and software server set up long interface channel, and ask software server to generate clean boot parameter.Software server configures the first database with the related information of the link information three of storage security start-up parameter, accounts information and long interface channel, and returns the clean boot parameter of generation.This clean boot parameter, by the forwarding of system client, is sent to system server by software client, and Request System server generates scrip.System server configures the second database to store the incidence relation of scrip, clean boot parameter and logging on authentication three corresponding to account information.After software client receives the scrip returned, software server is sent to by long interface channel, software server is according to the long link information connecting communication, inquire about the first database, obtain the first clean boot parameter, and the first clean boot parameter and scrip are sent to system server.System server confirm this scrip and the first clean boot parameter consistent with the data of the second database purchase after, logging on authentication is sent to software server, uses logging on authentication to account server request login authentication to enable software server.Software client is at logging on authentication by after certification, and use account information registration is to software server.Need rely on browser or need repeatedly to input account number cipher compared to prior art, the multi-client that the present invention is same system of account logs in and provides safe automatic login, decreases user operation, improves fail safe.
Further, software client of the present invention and system client are when setting up local interface channel, first carry out handshake authentication, just login process is started after handshake authentication success, ensure that the legitimacy of software client, prevent rogue program to disguise oneself as legitimate client, improve the fail safe logged in further.
Further, when system client first time of the present invention signs in system server, verified the legitimacy of accounts information by account server, and send logging on authentication to system client, be transmitted to system server by system client and store.Then system client deletes this logging on authentication, and in follow-up login process, system client and software client all can not receive this logging on authentication, prevents logging on authentication stolen on the client.And system client storage is generated and the log-on message returned by system server, the hardware characteristics information of the machine is used to be encrypted, login process afterwards completes automatic login by this log-on message, not only ensure that the convenience automatically logged in, and improves the fail safe of login.
Accompanying drawing explanation
Fig. 1 is the schematic flow sheet of a kind of embodiment of login method provided by the invention;
Fig. 2 is the schematic flow sheet of the another kind of embodiment of login method provided by the invention;
Fig. 3 is the schematic flow sheet of another embodiment of login method provided by the invention;
Fig. 4 is the structural representation of a kind of embodiment of terminal equipment provided by the invention;
Fig. 5 is the structural representation of the another kind of embodiment of terminal equipment provided by the invention;
Fig. 6 is the structural representation of another embodiment of terminal equipment provided by the invention;
Fig. 7 is the structural representation of a kind of embodiment of communication system provided by the invention;
Fig. 8 is the schematic flow sheet of step S1 to step S2 that communication system provided by the invention carries out information interaction;
Fig. 9 is the schematic flow sheet of step S3 to step S4 that communication system provided by the invention carries out information interaction;
Figure 10 is the schematic flow sheet of step S5 to step S6 that communication system provided by the invention carries out information interaction.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Embodiment 1
See Fig. 1, it is the schematic flow sheet of a kind of embodiment of login method provided by the invention.This login method is applicable to terminal equipment, and this terminal equipment configuration has software client and system client, and it mainly comprises step 101 to step 107, specific as follows:
Step 101: software client and system client set up local interface channel, and by accounts information that local interface channel receiving system client terminal provides; Wherein, software client and system client are configured in same terminal equipment, and system client has used account information to be successfully logged onto system server, stores the logging on authentication corresponding with account information in system server.
In the present embodiment, each client with enjoying same set of system of account, and passes through each account of account service management.Account server can verify that whether the accounts information of each account is effective, and generates corresponding logging on authentication for each account.Logging on authentication can be any data that may be used for logging in such as user cipher, token.
In the present embodiment, software client and system client set up this interface channel, and by the accounts information that local interface channel receiving system client terminal provides, are specially: the link information of the local interface channel that software client receiving system client terminal sends; Software client, according to the link information of local interface channel, sends handshake authentication information to system client, carries out handshake authentication with Request System client; Software client after legal by system client certification, sets up local interface channel with system client, and by accounts information that local interface channel receiving system client terminal provides.
In the present embodiment, local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.The present embodiment is illustrated the Establishing process of local interface channel with local port passage.The local port number of Stochastic choice is sent to software client by system client, to notify connectivity port required for software client, thus ensures that rogue program cannot be connected to system client by fixed port.Software client is connected to this local port, sends handshake authentication information by cipher mode to system client, with its legal identity of Request System client validation, prevents rogue program to disguise oneself as when knowing local port software client.If shake hands unsuccessfully, then system client can disconnect automatically, stops login process.After handshake authentication passes through, software client and system client are set up local port and are connected, all communication datas of two clients all after encryption, communicated by this local port, even if thus ensure that the process of software client is replaced order and the data of the legitimate client receiving system client terminal transmission that can not disguise oneself as at connection procedure by malice.
Step 102: software client sends logging request to software server, sets up long interface channel with software server; Wherein, logging request comprises account information.
In the present embodiment, after long interface channel between software client and software service is successfully established, software server will lock account information, and the account data interaction of subsequent login process of information need be just valid data by this long interface channel transmission, ensure that the fail safe of login.
Step 103: software client receives the clean boot parameter of software server transmission by long interface channel; Wherein, in software server, be configured with the first database, for the related information of the link information three of storage security start-up parameter, accounts information and long interface channel.
In the present embodiment, after long interface channel is set up, software client sends the generation request of clean boot parameter to software server.Software server, after this generation request of reception, certainly increases variable according to the mark of this software server and of this software server, generates clean boot parameter, to ensure the global uniqueness of this clean boot parameter according to the create-rule preset.For example software server be designated A, being 1001 from increasing variable, can be A1001 by clean boot setting parameter, owing to can constantly increase from increasing variable, therefore can ensure the global uniqueness of clean boot parameter.
In the present embodiment, in software server, be configured with the first database, for the related information of the link information three of storage security start-up parameter, accounts information and long interface channel.Wherein, the link information relationship maps one by one of accounts information and long interface channel, the link information of long interface channel and this clean boot parameter relationship maps one by one.
Step 104: software client sends scrip application request to system client; Wherein, scrip application request comprises clean boot parameter.
In the present embodiment, after software client receives clean boot parameter, parameter is it can be used as to send scrip application request to system client.This scrip application request can be, but not limited to the software identification also comprising software client.
Step 105: scrip application request forward to system server, is generated scrip with Request System server, and scrip is returned to system client by system client; Wherein, in system server, be configured with the second database, for storing the related information of scrip, clean boot parameter and logging on authentication three.
In the present embodiment, the scrip of generation is 32 readable random strings, and within effective time only can certification once.This scrip is provided with effective time, is shorter than the connect hours of long interface channel this effective time.When long interface channel disconnects or when not re-using this long interface channel, scrip also will lose efficacy.In addition, other software clients use this scrip that it also can be made to lose efficacy.
In this enforcement, system server is configured with the second database, for storing the related information of scrip, clean boot parameter and logging on authentication three.Scrip respectively with clean boot parameter, logging on authentication mapping association one by one, guarantee the fail safe of scrip.
Step 106: the scrip that software client receiving system client terminal forwards, and by long interface channel, this scrip is sent to software server, to make software server according to the link information of long interface channel, inquire about the first database, obtain the first clean boot parameter, and send logging on authentication application request to system server; Wherein, logging on authentication application request comprises the first clean boot parameter and scrip, thus make system server inquire about the second database according to this scrip, obtain the second clean boot parameter, and confirmation first clean boot parameter and the second clean boot parameter consistent time, logging on authentication associated by this scrip is sent to software server, uses the logging on authentication of association to account server request login authentication to enable software server.
In the present embodiment, software client obtains this scrip by local interface channel, and is stored in internal memory, then this scrip is transmitted to software server.Software server receives this scrip by long interface channel, and inquires about the first database according to the link information of long interface channel, obtains the first clean boot parameter.Therefore, only have and keep this long interface channel, software server could obtain correct clean boot parameter, and other illegal interface channels can not complete login process.
In the present embodiment, the first clean boot parameter obtained and scrip are sent logging on authentication application request as parameter to system server by software server.System server can check the validity of scrip and the first clean boot parameter simultaneously, and the software client that this scrip can only be applied used, even if also will be lost efficacy by malicious intercepted.System server inquires about the second database according to scrip, obtains the second clean boot parameter and the logging on authentication associated, relatively and confirm the first clean boot parameter and the second clean boot parameter consistent time, logging on authentication is returned to software server.
In the present embodiment, the communication interface of system server to software server limits, and only has believable software server to access, and ensure that user profile can not be revealed to the third party of malice.And the communication environment of server all rests in service provider on hand, ensure the transmission security of user's voucher further by the technology such as fire compartment wall or encryption tunnel.
Step 107: software client is after the logging on authentication of association passes through certification, and the information registration that accesses to your account is to software server.
In the present embodiment, software server communicates with account server, with the validity of this logging on authentication of requests verification after obtaining logging on authentication.Because Accounting system stores the logging on authentication of each account, the result is also returned to software server after comparison by inquiry.If the verification passes, then software server accept software client use the account information log in, otherwise, terminate login process.
In addition, software client can support the compatible login mode of rollback in the present invention.If above-mentioned steps performs unsuccessfully or after the failure of effective retry, software client can return back to original login interface voluntarily, manually inputted accounts information to log in by user, thus also can not have influence on the normal login of software client when ensure that system client or system server go wrong.
One as the present embodiment is illustrated, and is the schematic flow sheet of the another kind of embodiment of login method provided by the invention see Fig. 2, Fig. 2.The difference of Fig. 2 and Fig. 1 is, also comprises step 201 ~ 204 before step 101, and its concrete steps are as follows:
Step 201: accounts information is sent to account server by system client, to ask account server to verify accounts information, and generates the logging on authentication corresponding with account information after being proved to be successful.
Step 202: system client receives this logging on authentication, and is saved in internal memory.
Step 203: logging on authentication is transmitted to system server by system client, to make system server to the legitimacy of account server requests verification logging on authentication, and after logging on authentication is verified, stores this logging on authentication.
Step 204: after the logging on authentication that system client receiving system server returns verifies legal information, delete this logging on authentication from internal memory, and the information registration that accesses to your account is to system server.
In this citing, system client carries out communication by https mode and system server, account server.The logging on authentication that system client sends is sent to account server by system server, to ask account server to verify its legitimacy, and after being verified, stores this logging on authentication.System client returns after logging on authentication verifies legal message at system server, delete this logging on authentication, and the information registration that accesses to your account is to system server.Logging on authentication is only kept in system server and account server, ensures that logging on authentication can not cause revealing due to the environmental problem of software client or system client, improves the fail safe of login.
In this citing, the transmission channel by safety communicates with account server by system server, and as https mode or limiting access ip mode, thus safeguards system server and account server are to the fail safe of logging on authentication certification.
In this citing, the term of validity of logging on authentication can be never expired or have expired restriction, loses efficacy afterwards as 30 days.For never expired situation, do not affect login authentication process, and for terminable logging on authentication, system server can preserve logging on authentication always, until replaced by new voucher, once logging on authentication is expired, system server by automatic inspection to this situation, then reporting system client logs credential expires, allows user again manually carry out login authentication operation, namely returns step 201.
One as the present embodiment is illustrated, and is the schematic flow sheet of another embodiment of login method provided by the invention see Fig. 3, Fig. 3.The difference of Fig. 3 and Fig. 2 is, after step 204, also comprises step 301 ~ 302, and its step is specific as follows:
Step 301: system client is the log-on message that sends of receiving system server also, and uses the hardware characteristics information of native system client be encrypted log-on message and store;
When step 302 system client needs to carry out automatic login authentication, log-on message is sent to system server, to make system server after checking log-on message is legal, accept system client and use user account automatically to log in.
In this citing, system server is by stochastic generation log-on message and return to system client, and system client uses the hardware characteristics information of this client be encrypted log-on message and store.In automatic login process after system client, carry out certification by this log-on message, again input user account password without the need to user, reduce the operation of user.And when system client execution logs in automatically, hardware characteristics information does not meet and system client will be caused to refuse to log in, and when only having hardware characteristics information conforms, correspondence system client correctly could read log-on message, and log-on message is put into internal memory.Complete automatically log in after eliminate this log-on message immediately, even if ensure that the local log-on message stored is stolen can not carry out Account Logon on other equipment by Malware, effectively prevent log-on message to be stolen and problem that user account is stolen.
Therefore the login method that the embodiment of the present invention provides, after the system client information of accessing to your account is successfully logged onto system device, software client and system client set up local interface channel, and acquisition account information also starts login process.Software client and software server set up long interface channel, and ask software server to generate clean boot parameter.Software server configures the first database with the related information of the link information three of storage security start-up parameter, accounts information and long interface channel, and returns the clean boot parameter of generation.This clean boot parameter, by the forwarding of system client, is sent to system server by software client, and Request System server generates scrip.System server configures the second database to store the incidence relation of scrip, clean boot parameter and logging on authentication three corresponding to account information.After software client receives the scrip returned, software server is sent to by long interface channel, software server is according to the long link information connecting communication, inquire about the first database, obtain the first clean boot parameter, and the first clean boot parameter and scrip are sent to system server.System server confirm this scrip and the first clean boot parameter consistent with the data of the second database purchase after, logging on authentication is sent to software server, uses logging on authentication to account server request login authentication to enable software server.Software client is at logging on authentication by after certification, and use account information registration is to software server.Need rely on browser or need repeatedly to input account number cipher compared to prior art, the multi-client that the present invention is same system of account logs in and provides safe automatic login, decreases user operation, improves fail safe.
Further, software client of the present invention and system client are when setting up local interface channel, first carry out handshake authentication, just login process is started after handshake authentication success, ensure that the legitimacy of software client, prevent rogue program to disguise oneself as legitimate client, improve the fail safe logged in further.
Further, when system client first time of the present invention signs in system server, verified the legitimacy of accounts information by account server, and send logging on authentication to system client, be transmitted to system server by system client and store.Then system client deletes this logging on authentication, and in follow-up login process, system client and software client all can not receive this logging on authentication, prevents logging on authentication stolen on the client.And system client storage is generated and the log-on message returned by system server, the hardware characteristics information of the machine is used to be encrypted, login process afterwards completes automatic login by this log-on message, not only ensure that the convenience automatically logged in, and improves the fail safe of login.
Embodiment 2
Be the structural representation of a kind of embodiment of terminal equipment provided by the invention see Fig. 4, Fig. 4, as shown in Figure 4, in this terminal equipment, be configured with software client 1 and system client 2.Software client 1 comprises: local connection construction unit 11, long construction unit 12, first receiving element 13, first transmitting element 14, second receiving element 15, first that connects log in unit 16.System client 2 comprises: the second transmitting element 21.
Local connect construction unit 11, for setting up local interface channel with system client 2, and by accounts information that local interface channel receiving system client terminal 2 provides; Wherein, system client 2 has used account information to be successfully logged onto system server, stores the logging on authentication corresponding with accounts information in system server.
Long connection construction unit 12, for sending logging request to software server, sets up long interface channel with software server; Wherein, logging request comprises account information.
First receiving element 13, for receiving the clean boot parameter that software server sends by long interface channel; Wherein, in software server, be configured with the first database, for the related information of the link information three of storage security start-up parameter, accounts information and long interface channel.
First transmitting element 14, for sending scrip application request to system client 2; Wherein, scrip application request comprises this clean boot parameter.
Second transmitting element 21, for by scrip application request forward to system server, generate scrip with Request System server, and scrip returned to system client 2; Wherein, in system server, be configured with the second database, for storing the related information of scrip, clean boot parameter and logging on authentication three.
Second receiving element 15, for the scrip that receiving system client terminal 2 forwards, and by long interface channel, scrip is sent to software server, to make software server according to the link information of long interface channel, inquire about the first database, obtain the first clean boot parameter, and send logging on authentication application request to system server; Wherein, logging on authentication application request comprises the first clean boot parameter and scrip, thus make system server inquire about the second database according to scrip, obtain the second clean boot parameter, and confirmation first clean boot parameter and the second clean boot parameter consistent time, logging on authentication associated by scrip is sent to software server, uses the logging on authentication of association to account server request login authentication to enable software server;
First logs in unit 16, and for the logging on authentication in association by after certification, the information registration that accesses to your account is to software server.
In the present embodiment, the local construction unit 11 that connects comprises: first receives subelement, the first transmission subelement builds subelement with local connection.Wherein, first the link information of subelement for the local interface channel of receiving system client terminal 2 transmission is received.First sends subelement for the link information according to local interface channel, sends handshake authentication information, carry out handshake authentication with Request System client 2 to system client 2.Local connection builds subelement, for after legal by system client 2 certification, sets up local interface channel with system client 2, and by accounts information that local interface channel receiving system client terminal 2 provides.
In the present embodiment, local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.
One as the present embodiment is illustrated, and is the structural representation of the another kind of embodiment of terminal equipment provided by the invention see Fig. 5, Fig. 5.The difference of Fig. 5 and Fig. 4 is, system client 2 also comprises: the 3rd transmitting element 22, the 3rd receiving element 23, the 4th transmitting element 24 and second log in unit 25.Wherein, accounts information, for before local interface channel foundation, is sent to account server by the 3rd transmitting element 22, to ask account server to verify accounts information, and generates the logging on authentication corresponding with accounts information after being proved to be successful.3rd receiving element 23 for receiving logging on authentication, and is saved in internal memory.4th transmitting element 24, for logging on authentication is transmitted to system server, to make system server to the legitimacy of account server requests verification logging on authentication, and after logging on authentication is verified, stores this logging on authentication.Second logs in after unit 25 verifies legal information for the logging on authentication that receiving system server returns, and deletes this logging on authentication from internal memory, and uses account information registration to system server.
As one citing of the present invention, be the structural representation of another embodiment of terminal equipment provided by the invention see Fig. 6, Fig. 6.The difference of Fig. 6 and Fig. 5 is, system client 2 also comprises: the 4th receiving element 26 and the 3rd logs in unit 27.Wherein, the 4th receiving element 26 accesses to your account after information registration to system server for logging in unit 25 second, the log-on message that receiving system server sends, and uses the hardware characteristics information of native system client be encrypted log-on message and store.3rd logs in unit 27 for when needs carry out automatic login authentication, and this log-on message is sent to system server, to make system server after checking log-on message is legal, accepts system client and uses this user account automatically to log in.
The more detailed steps flow chart of the present embodiment and operation principle can be, but not limited to the relevant record see embodiment 1.
Therefore the terminal equipment that the embodiment of the present invention provides, after the system client information of accessing to your account is successfully logged onto system device, software client and system client set up local interface channel, and acquisition account information also starts login process.Software client and software server set up long interface channel, and ask software server to generate clean boot parameter.Software server configures the first database with the related information of the link information three of storage security start-up parameter, accounts information and long interface channel, and returns the clean boot parameter of generation.This clean boot parameter, by the forwarding of system client, is sent to system server by software client, and Request System server generates scrip.System server configures the second database to store the incidence relation of scrip, clean boot parameter and logging on authentication three corresponding to account information.After software client receives the scrip returned, software server is sent to by long interface channel, software server is according to the long link information connecting communication, inquire about the first database, obtain the first clean boot parameter, and the first clean boot parameter and scrip are sent to system server.System server confirm this scrip and the first clean boot parameter consistent with the data of the second database purchase after, logging on authentication is sent to software server, uses logging on authentication to account server request login authentication to enable software server.Software client is at logging on authentication by after certification, and use account information registration is to software server.Need rely on browser or need repeatedly to input account number cipher compared to prior art, the multi-client that the present invention is same system of account logs in and provides safe automatic login, decreases user operation, improves fail safe.
Embodiment 3
It is the structural representation of a kind of embodiment of communication system provided by the invention see Fig. 7, Fig. 7.As shown in Figure 7, this communication system comprises: account server 701, system server 702, software server 703 and terminal equipment 704.Wherein, the detailed construction of terminal equipment 704 and operation principle can be, but not limited to the relevant record being illustrated in embodiment 1 and embodiment 2.
Below in conjunction with Fig. 8 to Figure 10, the flow process that the present embodiment provides communication system to carry out information interaction is described in detail.The flow process that this communication system carries out information interaction mainly comprises step S1 to step S6, specific as follows:
S1, the system client information of accessing to your account is successfully logged onto system server, and system server stores logging on authentication.
S2, software client and system client carry out Handshake Protocol certification, set up local interface channel after the authentication has been successful.
S3, software client and software server set up long interface channel, and to software server application clean boot parameter.
S4, scrip to system server application scrip, and is transmitted to software server by system client by software client.
S5, software server, to system server application logging on authentication, receives logging on authentication after system server is verified.
S6, software server and account server communication, requests verification logging on authentication, after logging on authentication is verified, accepts the login of software client.
In order to the information interaction flow process of this communication system is better described, below the detailed process of step is described.
See Fig. 8, be the schematic flow sheet of step S1 to step S2 that communication system provided by the invention carries out information interaction.
Step S1, the system client information of accessing to your account is successfully logged onto system server, and system server stores logging on authentication, specifically comprises step S11 to step S19, as follows:
S11, system client communicates with account server, requests verification user name password.
S12, after account server is verified, generates and preserves logging on authentication, and logging on authentication is sent to system client.
S13, logging on authentication is saved in internal memory by system client.
S14, logging on authentication is sent to system server by system client.
S15, system server communicates with account server, requests verification logging on authentication.
S16, account server returns the result to system server.
S17, system server, after logging on authentication is verified, preserves logging on authentication.
S18, system server sends login success message to system client, and this message comprises log-on message, and log-on message is used for the later automatic login process of system client.
S19, system client deletes the logging on authentication in internal memory, and uses the hardware characteristics information of native system client be encrypted log-on message and preserve.
Step S2, software client and system client carry out Handshake Protocol certification, set up local interface channel after the authentication has been successful, specifically comprise step S21 to step S24, as follows:
S21, system client sends locally-attached link information to software client.
S22, software client, according to this link information, sends handshake authentication information to system client.
S23, the legitimacy of system client inspection software client.
S24, system client, by after handshake authentication, is set up local connection with software client, and is returned accounts information to software client.
See Fig. 9, be the schematic flow sheet of step S3 to step S4 that communication system provided by the invention carries out information interaction.
Step S3, software client and software server set up long interface channel, and to software server application clean boot parameter, specifically comprise step S31 to step S35, as follows:
S31, software client sends logging request to software server, and this logging request comprises accounts information.
S32, software client and software server set up long interface channel, and the link information of accounts information and long interface channel stores and is associated in the first database by software server.
S33, software client is to software server application clean boot parameter.
S34, software server generates and preserves clean boot parameter, and the link information of clean boot parameter with long interface channel is associated in the first database.
S35, software server returns clean boot parameter to software client.
Scrip to system server application scrip, and is transmitted to software server by system client by step S4 software client, specifically comprises step S41 to step S45, as follows:
S41, software client sends the application request of scrip to system client, and this application request comprises identification information and the clean boot parameter of software client.
S42, system client by the application request forward of scrip to system server.
S43, system server generates scrip, and in the second database, is associated respectively by scrip with clean boot parameter and logging on authentication.
S44, system server returns the scrip of generation to system client.
S45, scrip is transmitted to software client by system client.
See Figure 10, be the schematic flow sheet of step S5 to step S6 that communication system provided by the invention carries out information interaction.
Step S5, software server, to system server application logging on authentication, receives logging on authentication after system server is verified, and specifically comprises step S51 to step S55, as follows:
S51, software client sends scrip by long interface channel to software server.
S52, software server, according to the link information of long interface channel, inquires about the first database, obtains the first corresponding clean boot parameter.
S53, software server sends the application request of logging on authentication to system server, and this application request comprises the first clean boot parameter and scrip.
S54, system server, according to scrip, inquires about the second database, the second clean boot parameter and logging on authentication associated by acquisition, and verifies that whether the second clean boot parameter is consistent with the first clean boot parameter.
S55, if so, then system server sends logging on authentication associated by this scrip to software server, otherwise, stop login process.
Step S6, software server and account server communication, requests verification logging on authentication, after logging on authentication is verified, accepts the login of software client, specifically comprises step S61 to step S64, as follows:
S61, software server is to account server requests verification logging on authentication.
S62, the legitimacy of account server checking logging on authentication.
S63, account server returns the result to software server.
S64, if the verification passes, then software server accepts the login of software client.
The more detailed steps flow chart of the present embodiment can be, but not limited to the relevant record see embodiment 1.
Therefore the communication system that the embodiment of the present invention provides, after the system client information of accessing to your account is successfully logged onto system device, software client and system client set up local interface channel, and acquisition account information also starts login process.Software client and software server set up long interface channel, and ask software server to generate clean boot parameter.Software server configures the first database with the related information of the link information three of storage security start-up parameter, accounts information and long interface channel, and returns the clean boot parameter of generation.This clean boot parameter, by the forwarding of system client, is sent to system server by software client, and Request System server generates scrip.System server configures the second database to store the incidence relation of scrip, clean boot parameter and logging on authentication three corresponding to account information.After software client receives the scrip returned, software server is sent to by long interface channel, software server is according to the long link information connecting communication, inquire about the first database, obtain the first clean boot parameter, and the first clean boot parameter and scrip are sent to system server.System server confirm this scrip and the first clean boot parameter consistent with the data of the second database purchase after, logging on authentication is sent to software server, uses logging on authentication to account server request login authentication to enable software server.Software client is at logging on authentication by after certification, and use account information registration is to software server.Need rely on browser or need repeatedly to input account number cipher compared to prior art, the multi-client that the present invention is same system of account logs in and provides safe automatic login, decreases user operation, improves fail safe.
One of ordinary skill in the art will appreciate that all or part of flow process realized in above-described embodiment method, that the hardware that can carry out instruction relevant by computer program has come, described program can be stored in a computer read/write memory medium, this program, when performing, can comprise the flow process of the embodiment as above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-OnlyMemory, ROM) or random store-memory body (RandomAccessMemory, RAM) etc.
The above is the preferred embodiment of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications are also considered as protection scope of the present invention.
Claims (15)
1. a login method, is characterized in that, comprising:
Software client and system client set up local interface channel, and receive by described local interface channel the accounts information that described system client provides; Wherein, described software client and described system client are configured in same terminal equipment, and described system client has used described accounts information to be successfully logged onto system server, stores the logging on authentication corresponding with described accounts information in described system server;
Described software client sends logging request to software server, sets up long interface channel with described software server; Wherein, described logging request comprises described accounts information;
Described software client receives the clean boot parameter of described software server transmission by described long interface channel; Wherein, in described software server, be configured with the first database, for storing the related information of the link information three of described clean boot parameter, described accounts information and described long interface channel;
Described software client sends scrip application request to described system client; Wherein, described scrip application request comprises described clean boot parameter;
Described scrip application request forward is given described system server by described system client, to ask described system server to generate scrip, and described scrip is returned to described system client; Wherein, in described system server, be configured with the second database, for storing the related information of described scrip, described clean boot parameter and described logging on authentication three;
Described software client receives the described scrip that described system client forwards, and by described long interface channel, described scrip is sent to described software server, to make described software server according to the link information of described long interface channel, inquire about described first database, obtain the first clean boot parameter, and send logging on authentication application request to described system server; Wherein, described logging on authentication application request comprises described first clean boot parameter and described scrip, thus make described system server according to described second database of described scrip inquiry, obtain the second clean boot parameter, and when confirming described first clean boot parameter and described second clean boot parameter is consistent, logging on authentication associated by described scrip is sent to described software server, uses the logging on authentication of described association to account server request login authentication to enable described software server;
Described software client, after the logging on authentication of described association passes through certification, uses described accounts information to sign in described software server.
2. login method according to claim 1, is characterized in that, described software client and system client set up local interface channel, and receives by described local interface channel the accounts information that described system client provides, and specifically comprises:
Described software client receives the link information of the local interface channel that described system client sends;
Described software client, according to the link information of described local interface channel, sends handshake authentication information to described system client, carries out handshake authentication to ask described system client;
Described software client after legal by described system client certification, sets up described local interface channel with described system client, and receives by described local interface channel the accounts information that described system client provides.
3. login method according to claim 1 and 2, is characterized in that, described local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.
4. login method according to claim 1, is characterized in that, before described software client and system client set up local interface channel, also comprises:
Described accounts information is sent to account server by described system client, to ask described account server to verify described accounts information, and generates the logging on authentication corresponding with described accounts information after being proved to be successful;
Described system client receives described logging on authentication, and is saved in internal memory;
Described logging on authentication is transmitted to described system server by described system client, to make described system server to the legitimacy of logging on authentication described in described account server requests verification, and after described logging on authentication is verified, stores described logging on authentication;
Described system client receives after logging on authentication that described system server returns verifies legal information, deletes described logging on authentication, and use described accounts information to sign in described system server from internal memory.
5. login method according to claim 4, is characterized in that, uses after described accounts information signs in described system server, also comprise at described system client:
Described system client also receives the log-on message that described system server sends, and uses the hardware characteristics information of native system client be encrypted described log-on message and store;
When described system client needs to carry out automatic login authentication, described log-on message is sent to described system server, to make described system server after the described log-on message of checking is legal, accept described system client and use described user account automatically to log in.
6. login method according to claim 1, is characterized in that, described clean boot parameter increases variable by described software server certainly according to one of the mark of this software server and this software server, generates according to the create-rule preset.
7. login method according to claim 1, is characterized in that, described scrip is 32 readable random strings, and within effective time only can certification once;
Wherein, the connect hours of described long interface channel is shorter than described effective time.
8. a terminal equipment, is characterized in that, is configured with software client and system client in described terminal equipment;
Described software client comprises:
Local connecting construction unit, for setting up local interface channel with described system client, and receiving by described local interface channel the accounts information that described system client provides; Wherein, described system client has used described accounts information to be successfully logged onto system server, stores the logging on authentication corresponding with described accounts information in described system server;
Long connection construction unit, for sending logging request to software server, sets up long interface channel with described software server; Wherein, described logging request comprises described accounts information;
First receiving element, for receiving the clean boot parameter that described software server sends by described long interface channel; Wherein, in described software server, be configured with the first database, for storing the related information of the link information three of described clean boot parameter, described accounts information and described long interface channel;
With, the first transmitting element, for sending scrip application request to described system client; Wherein, described scrip application request comprises described clean boot parameter;
Described system client comprises: the second transmitting element;
Described second transmitting element is used for by described scrip application request forward to described system server, to ask described system server to generate scrip, and described scrip is returned to described system client; Wherein, in described system server, be configured with the second database, for storing the related information of described scrip, described clean boot parameter and described logging on authentication three;
Described software client also comprises:
Second receiving element, for receiving the described scrip that described system client forwards, and by described long interface channel, described scrip is sent to described software server, to make described software server according to the link information of described long interface channel, inquire about described first database, obtain the first clean boot parameter, and send logging on authentication application request to described system server; Wherein, described logging on authentication application request comprises described first clean boot parameter and described scrip, thus make described system server according to described second database of described scrip inquiry, obtain the second clean boot parameter, and when confirming described first clean boot parameter and described second clean boot parameter is consistent, logging on authentication associated by described scrip is sent to described software server, uses the logging on authentication of described association to account server request login authentication to enable described software server;
With, first logs in unit, for the logging on authentication in described association by after certification, uses described accounts information to sign in described software server.
9. terminal equipment according to claim 8, is characterized in that, described this locality connects construction unit and comprises:
First receives subelement, for receiving the link information of the local interface channel that described system client sends;
First sends subelement, for the link information according to described local interface channel, sends handshake authentication information, carry out handshake authentication to ask described system client to described system client;
With, local connection builds subelement, for after legal by described system client certification, sets up described local interface channel with described system client, and receives by described local interface channel the accounts information that described system client provides.
10. terminal equipment according to claim 8 or claim 9, is characterized in that, described local interface channel is local port passage, pipeline name interface channel, Message queue interface channel or internal memory Share interlinkage passage.
11. terminal equipments according to claim 8, is characterized in that, described system client also comprises:
3rd transmitting element, before setting up at described local interface channel, described accounts information is sent to account server, to ask described account server to verify described accounts information, and generates the logging on authentication corresponding with described accounts information after being proved to be successful;
3rd receiving element, for receiving described logging on authentication, and is saved in internal memory;
4th transmitting element, for described logging on authentication is transmitted to described system server, to make described system server to the legitimacy of logging on authentication described in described account server requests verification, and after described logging on authentication is verified, store described logging on authentication;
With, second logs in unit, after the logging on authentication returned verifies legal information, deletes described logging on authentication from internal memory, and use described accounts information to sign in described system server for receiving described system server.
12., according to terminal equipment described in claim 11, is characterized in that, described system client also comprises:
4th receiving element, use after described accounts information signs in described system server for logging in unit described second, receive the log-on message that described system server sends, and use the hardware characteristics information of native system client be encrypted described log-on message and store;
With, 3rd logs in unit, for when needs carry out automatic login authentication, described log-on message is sent to described system server, to make described system server after the described log-on message of checking is legal, accept described system client and use described user account automatically to log in.
13. terminal equipments according to claim 8, is characterized in that, described clean boot parameter increases variable by described software server certainly according to one of the mark of this software server and this software server, generates according to the create-rule preset.
14. terminal equipments according to claim 8, is characterized in that, described scrip is 32 readable random strings, and within effective time only can certification once;
Wherein, the connect hours of described long interface channel is shorter than described effective time.
15. 1 kinds of communication systems, is characterized in that, comprise account server, system server, software server and the terminal equipment as described in any one of right 8 to 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510966911.4A CN105516163B (en) | 2015-12-18 | 2015-12-18 | A kind of login method and terminal device and communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510966911.4A CN105516163B (en) | 2015-12-18 | 2015-12-18 | A kind of login method and terminal device and communication system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105516163A true CN105516163A (en) | 2016-04-20 |
| CN105516163B CN105516163B (en) | 2019-02-12 |
Family
ID=55723799
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510966911.4A Active CN105516163B (en) | 2015-12-18 | 2015-12-18 | A kind of login method and terminal device and communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105516163B (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293349A (en) * | 2016-08-17 | 2017-01-04 | 北京拓盛智联技术有限公司 | A kind of terminal applies call method and device |
| CN107395578A (en) * | 2017-07-06 | 2017-11-24 | 福建天晴数码有限公司 | A kind of login method and terminal |
| CN107438069A (en) * | 2017-07-06 | 2017-12-05 | 福建天晴数码有限公司 | A kind of authorization method and terminal |
| CN107454061A (en) * | 2017-07-06 | 2017-12-08 | 福建天晴数码有限公司 | A kind of login method and system |
| CN107483400A (en) * | 2017-07-06 | 2017-12-15 | 福建天晴数码有限公司 | A kind of login method and terminal |
| CN107566421A (en) * | 2017-10-30 | 2018-01-09 | 江西博瑞彤芸科技有限公司 | A kind of login method |
| CN108573552A (en) * | 2017-03-09 | 2018-09-25 | 丰田自动车株式会社 | Locking and system for unlocking and key unit |
| CN109257370A (en) * | 2018-10-22 | 2019-01-22 | 武汉极意网络科技有限公司 | The processing system of checking request |
| CN109981312A (en) * | 2017-12-27 | 2019-07-05 | 杭州萤石软件有限公司 | intelligent device configuration method, device and system |
| CN111262869A (en) * | 2020-01-17 | 2020-06-09 | 珠海格力电器股份有限公司 | Login method, storage medium and computer equipment |
| CN111506553A (en) * | 2019-01-31 | 2020-08-07 | 阿里巴巴集团控股有限公司 | Database function setting method and device |
| CN113487811A (en) * | 2016-08-30 | 2021-10-08 | Ncr公司 | Secure process emulation detection |
| CN116684467A (en) * | 2023-08-02 | 2023-09-01 | 武汉吧哒科技股份有限公司 | Data acquisition method, electronic device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120291114A1 (en) * | 2011-05-13 | 2012-11-15 | Cch Incorporated | Single sign-on between applications |
| CN103888451A (en) * | 2014-03-10 | 2014-06-25 | 百度在线网络技术（北京）有限公司 | Method, device and system for certification authorization |
| CN104113534A (en) * | 2014-07-02 | 2014-10-22 | 百度在线网络技术（北京）有限公司 | System and method for logging in applications (APPs) |
-
2015
- 2015-12-18 CN CN201510966911.4A patent/CN105516163B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120291114A1 (en) * | 2011-05-13 | 2012-11-15 | Cch Incorporated | Single sign-on between applications |
| CN103888451A (en) * | 2014-03-10 | 2014-06-25 | 百度在线网络技术（北京）有限公司 | Method, device and system for certification authorization |
| CN104113534A (en) * | 2014-07-02 | 2014-10-22 | 百度在线网络技术（北京）有限公司 | System and method for logging in applications (APPs) |
Non-Patent Citations (1)
| Title |
|---|
| 胡志高: "基于数字签名与J2EE的单点登录系统", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293349A (en) * | 2016-08-17 | 2017-01-04 | 北京拓盛智联技术有限公司 | A kind of terminal applies call method and device |
| CN106293349B (en) * | 2016-08-17 | 2019-08-27 | 北京拓盛智联技术有限公司 | A kind of terminal applies call method and device |
| CN113487811A (en) * | 2016-08-30 | 2021-10-08 | Ncr公司 | Secure process emulation detection |
| US11139973B2 (en) | 2017-03-09 | 2021-10-05 | Toyota Jidosha Kabushiki Kaisha | Locking and unlocking system and key unit |
| CN108573552A (en) * | 2017-03-09 | 2018-09-25 | 丰田自动车株式会社 | Locking and system for unlocking and key unit |
| CN108573552B (en) * | 2017-03-09 | 2022-02-22 | 丰田自动车株式会社 | Locking and unlocking system and key unit |
| CN107395578A (en) * | 2017-07-06 | 2017-11-24 | 福建天晴数码有限公司 | A kind of login method and terminal |
| CN107438069A (en) * | 2017-07-06 | 2017-12-05 | 福建天晴数码有限公司 | A kind of authorization method and terminal |
| CN107454061A (en) * | 2017-07-06 | 2017-12-08 | 福建天晴数码有限公司 | A kind of login method and system |
| CN107483400A (en) * | 2017-07-06 | 2017-12-15 | 福建天晴数码有限公司 | A kind of login method and terminal |
| CN107566421A (en) * | 2017-10-30 | 2018-01-09 | 江西博瑞彤芸科技有限公司 | A kind of login method |
| CN109981312A (en) * | 2017-12-27 | 2019-07-05 | 杭州萤石软件有限公司 | intelligent device configuration method, device and system |
| CN109257370B (en) * | 2018-10-22 | 2020-11-03 | 武汉极意网络科技有限公司 | Processing system for authentication request |
| CN109257370A (en) * | 2018-10-22 | 2019-01-22 | 武汉极意网络科技有限公司 | The processing system of checking request |
| CN111506553A (en) * | 2019-01-31 | 2020-08-07 | 阿里巴巴集团控股有限公司 | Database function setting method and device |
| CN111506553B (en) * | 2019-01-31 | 2023-07-04 | 阿里巴巴集团控股有限公司 | Function setting method and device for database |
| CN111262869A (en) * | 2020-01-17 | 2020-06-09 | 珠海格力电器股份有限公司 | Login method, storage medium and computer equipment |
| CN116684467A (en) * | 2023-08-02 | 2023-09-01 | 武汉吧哒科技股份有限公司 | Data acquisition method, electronic device and storage medium |
| CN116684467B (en) * | 2023-08-02 | 2023-10-27 | 武汉吧哒科技股份有限公司 | Data acquisition method, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105516163B (en) | 2019-02-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105516163A (en) | Login method, terminal device and communication system | |
| CN109561066B (en) | Data processing method and device, terminal and access point computer | |
| US11281762B2 (en) | Method and apparatus for facilitating the login of an account | |
| EP3120591B1 (en) | User identifier based device, identity and activity management system | |
| CN102201915B (en) | Terminal authentication method and device based on single sign-on | |
| CN107122674B (en) | Access method of oracle database applied to operation and maintenance auditing system | |
| CN108243176B (en) | Data transmission method and device | |
| CN105187431A (en) | Log-in method, server, client and communication system for third party application | |
| CN105721412A (en) | Method and device for authenticating identity between multiple systems | |
| JP6572750B2 (en) | Authentication control program, authentication control device, and authentication control method | |
| CN105262748A (en) | Wide area network user terminal identity authentication method and system | |
| US20240064021A1 (en) | Access control method, apparatus, network side device, terminal and blockchain node | |
| CN111786996B (en) | Cross-domain synchronous login state method and device and cross-domain synchronous login system | |
| CN109274579A (en) | It is a kind of that user's uniform authentication method is applied based on wechat platform more | |
| CN112929388B (en) | Network identity cross-device application rapid authentication method and system, and user agent device | |
| CN104270368A (en) | Authentication method, authentication server and authentication system | |
| CN109460647B (en) | Multi-device secure login method | |
| KR102062851B1 (en) | Single sign on service authentication method and system using token management demon | |
| CN111245791A (en) | Single sign-on method for realizing management and IT service through reverse proxy | |
| US9231932B2 (en) | Managing remote telephony device configuration | |
| CN114500074B (en) | Single-point system security access method and device and related equipment | |
| CN111723347B (en) | Identity authentication method, identity authentication device, electronic equipment and storage medium | |
| CN105100107A (en) | Method and device for authenticating proxy client account | |
| KR20140095050A (en) | Method and apparatus for supporting single sign-on in a mobile communication system | |
| EP4207682A1 (en) | Device, method and system of handling access control |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |