CN104753927A - Unified verification method and device - Google Patents
Unified verification method and device Download PDFInfo
- Publication number
- CN104753927A CN104753927A CN201510108571.1A CN201510108571A CN104753927A CN 104753927 A CN104753927 A CN 104753927A CN 201510108571 A CN201510108571 A CN 201510108571A CN 104753927 A CN104753927 A CN 104753927A
- Authority
- CN
- China
- Prior art keywords
- party application
- authentication
- credentials
- user
- authentication 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.)
- 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
-
- 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)
Abstract
The invention discloses a unified verification method and a unified verification device. The method comprises: an authentication client uses the user credential for verification of identity; the authentication client acquires the third party application list corresponding to the user credential; after starting the third party application, if the verification of identity of the authentication client is successful, judging whether the third party application is recorded in the third party application list or not, if the third party application is recorded in the third party application list, the authentication client informs the register credential of the third party application to the third party application, the third party application uses the register credential for performing login certification on the business server. In the embodiment, when a plurality of third party applications are corresponding to the same user credential, the verification of identity can be performed aiming at the user credential, the verification of identity is performed for one time for a plurality of application programs rather than using the user credential for performing verification of identity for many times, so that the user experience is improved and the right control of the third party application is convenient.
Description
Technical field
The present invention relates to communication technical field, especially relate to a kind of method and apparatus unifying to verify.
Background technology
For multiple application programs of same enterprise, often need to use same set of user rs credentials (as username information and encrypted message etc.) to carry out authentication, if the application program of enterprise is more, when then each application program inputs identical user rs credentials, the experience of user can be made to decline.Such as, as shown in Figure 1, three application programs of enterprise are respectively application program 1, application program 2 and application program 3, application program 1 needs to use user rs credentials A to AAA (Authentication Authorization Accounting, authentication and authorization charging) server carries out authentication, and after authentication success, to service server 1, carry out login authentication; Application program 2 needs to use on user rs credentials A to aaa server carries out authentication, and after authentication success, to service server 2, carries out login authentication; Application program 3 needs to use on user rs credentials A to aaa server carries out authentication, and after authentication success, to service server 3, carries out login authentication.In these cases, three application programs all have input on identical user rs credentials A to aaa server carries out authentication, and the experience of user is declined.
Summary of the invention
The embodiment of the present invention provides a kind of method unifying to verify, terminal equipment runs Authentication Client and multiple third-party application, the user rs credentials that described multiple third-party application is corresponding identical, and described method comprises:
Described Authentication Client utilizes described user rs credentials to carry out authentication;
Described Authentication Client obtains third-party application list corresponding to described user rs credentials, have recorded the third-party application using described user rs credentials to carry out authentication in described third-party application list;
After third-party application starts, if described Authentication Client authentication success, then described Authentication Client judges whether described third-party application is recorded in described third-party application list;
If so, the proof of Register of described third-party application is informed to described third-party application by described Authentication Client, is utilized on described the proof of Register to service server carry out login authentication by described third-party application.
Described Authentication Client utilizes described user rs credentials to carry out the process of authentication, specifically comprises:
Described Authentication Client utilizes in described user rs credentials to authentication and authorization charging aaa server and carries out authentication, and receives the authentication success/unsuccessful response message from described aaa server.
Described Authentication Client obtains the process of third-party application list corresponding to described user rs credentials, specifically comprise: described Authentication Client sends the message for asking the third-party application list using described user rs credentials authority to application authorization server, and receives the response message carrying described third-party application list from described application authorization server; Wherein, described application authorization server is configured with the third-party application list allowing the described user rs credentials of use to carry out the third-party application of authentication.
After described Authentication Client judges whether described third-party application is recorded in described third-party application list, described method comprises further:
If described third-party application is not recorded in described third-party application list, then described third-party application does not have authority to use the message notice of described user rs credentials to described third-party application by described Authentication Client, is known described user rs credentials can not be used to carry out authentication by described third-party application.
Described user rs credentials specifically comprises username information and encrypted message, and described the proof of Register is specially and logs in token or Cookie mark.
The embodiment of the present invention provides a kind of Authentication Client, terminal equipment runs Authentication Client and multiple third-party application, the user rs credentials that described multiple third-party application is corresponding identical, described Authentication Client comprises: authentication module, carries out authentication for utilizing described user rs credentials;
Acquisition module, for obtaining third-party application list corresponding to described user rs credentials, have recorded the third-party application using described user rs credentials to carry out authentication in described third-party application list;
Judge module, after starting at third-party application, if described authentication module authentication success, then judges whether described third-party application is recorded in described third-party application list;
Sending module, for when judged result is for being, informs to described third-party application by the proof of Register of third-party application, utilizes the proof of Register to carry out login authentication to service server by described third-party application.
Described authentication module, carries out authentication specifically for utilizing in described user rs credentials to authentication and authorization charging aaa server, and receives the authentication success/unsuccessful response message from described aaa server.
Described acquisition module, specifically for sending the message for asking the third-party application list using described user rs credentials authority to application authorization server, and receives the response message carrying described third-party application list from described application authorization server; Wherein, described application authorization server is configured with the third-party application list allowing the described user rs credentials of use to carry out the third-party application of authentication.
Described sending module, also for after judging whether described third-party application is recorded in described third-party application list, if described third-party application is not recorded in described third-party application list, then do not had by described third-party application authority to use the message notice of described user rs credentials to described third-party application, known by described third-party application and described user rs credentials can not be used to carry out authentication.
Described user rs credentials comprises username information and encrypted message, and described the proof of Register is for logging in token or Cookie mark.
Based on technique scheme, in the embodiment of the present invention, for multiple application programs of same enterprise, when the user rs credentials that multiple third-party application is corresponding identical, can carry out authentication for this user rs credentials, multiple application program only needs authentication once, does not need to use this user rs credentials repeatedly to carry out authentication, user-friendly, improve the experience of user.Allow to use user rs credentials to carry out the third-party application of authentication by configuration in third-party application list, which third-party application can be controlled and utilize this user rs credentials to carry out authentication, facilitate the control of authority of third-party application.
Accompanying drawing explanation
Fig. 1 is the schematic diagram that in prior art, multiple application program carries out authentication;
Fig. 2 is the schematic diagram that in the embodiment of the present invention, multiple application program carries out authentication;
Fig. 3 is a kind of method flow schematic diagram unifying to verify that the embodiment of the present invention provides;
Fig. 4 is the structural representation of a kind of Authentication Client that the embodiment of the present invention provides.
Embodiment
For problems of the prior art, embodiments provide a kind of method unifying to verify, be applied in the network comprising terminal equipment, service server, aaa server and application authorization server.Terminal equipment runs Authentication Client and multiple third-party application (i.e. APP), the user rs credentials that multiple third-party application is corresponding identical, this user rs credentials specifically includes but not limited to username information and encrypted message.
Take Fig. 2 as the application scenarios schematic diagram of the embodiment of the present invention, operating system platform (as: the iOS of terminal equipment, Android, Windows) on run Authentication Client, third-party application 1 (APP1), third-party application 2 (APP2), third-party application 3 (APP3).Aaa server is used for carrying out authentication to third-party application 1, third-party application 2, third-party application 3.Application authorization server is configured with and allows to use this user rs credentials to carry out the third-party application list of the third-party application of authentication, namely can authorize which third-party application that this user rs credentials can be used to carry out authentication by application authorization server.Such as, when application authorization server authorized third party application 1, third-party application 2 can use this user rs credentials to carry out authentication, then third-party application 1, third-party application 2 is comprised in third-party application list.Service server 1 is for carrying out login authentication to third-party application 1, and service server 2 is for carrying out login authentication to third-party application 2.Authentication Client is responsible for the authentication of third-party application, namely replaces third-party application to use in user rs credentials to aaa server and carries out authentication, and manage the authentication of third-party application.
Under above-mentioned application scenarios, as shown in Figure 3, the method for this unification checking specifically comprises the following steps:
Step 301, Authentication Client utilizes user rs credentials (the identical user rs credentials that namely multiple third-party application is corresponding, user rs credentials can as username information and encrypted message etc.) to carry out authentication.
In the embodiment of the present invention, Authentication Client utilizes user rs credentials to carry out the process of authentication, specifically include but not limited to as under type: Authentication Client utilizes in user rs credentials to aaa server and carries out authentication, and receive the authentication success/unsuccessful response message from aaa server.
Concrete, the user rs credentials such as username information and encrypted message is sent to aaa server by Authentication Client, aaa server utilizes the local username information that stores and encrypted message, from the username information of Authentication Client and encrypted message, carries out authentication to Authentication Client.If authentication success, then aaa server sends the successful response message of authentication to Authentication Client; If authentication is unsuccessful, then aaa server sends the unsuccessful response message of authentication to Authentication Client.
Step 302, Authentication Client obtains third-party application list corresponding to user rs credentials, have recorded the third-party application using this user rs credentials to carry out authentication in this third-party application list.
In the embodiment of the present invention, Authentication Client obtains the process of third-party application list corresponding to user rs credentials, specifically include but not limited to as under type: Authentication Client sends the message for asking the third-party application list using this user rs credentials authority to application authorization server, and receives the response message carrying third-party application list (wherein carrying the information of third-party application) of self-application authorization server.
Concrete, which third-party application application authorization server can authorize have permission and use user's unified login, namely third-party application mandate is carried out at application authorization server, the third-party application list allowing to use unified login function is set, namely comprise the third-party application using user rs credentials to carry out authentication in this third-party application list, suppose to comprise third-party application 1, third-party application 2 in this third-party application list.Based on this, Authentication Client, after authentication success, sends the message for asking the third-party application list using this user rs credentials authority to application authorization server.Application authorization server after receiving that message, by there being the third-party application list of rights of using to return to Authentication Client, comprises third-party application 1, third-party application 2 in this third-party application list.Authentication Client, after receiving third-party application list, is known third-party application 1, third-party application 2 can be used user rs credentials to carry out authentication.
Step 303, after third-party application starts, if Authentication Client authentication success, then Authentication Client judges whether this third-party application is recorded in third-party application list.If so, then Authentication Client can perform step 304; If not, then Authentication Client can perform step 305.
Step 304, the proof of Register of third-party application is informed to third-party application by Authentication Client, is utilized on this proof of Register to service server carry out login authentication by third-party application.
Step 305, third-party application does not have authority to use the message notice of user rs credentials to third-party application by Authentication Client, is known this user rs credentials can not be used to carry out authentication by third-party application.
In the embodiment of the present invention, third-party application start after, third-party application by software development kit to Authentication Client request authentication result.If Authentication Client does not also carry out authentication, then perform step 301 and step 302, carry out authentication by Authentication Client.If Authentication Client carries out authentication, then, when Authentication Client authentication is unsuccessful, conventionally process.If Authentication Client carries out authentication, then, when Authentication Client authentication success, Authentication Client judges whether third-party application is recorded in third-party application list.For third-party application 1, third-party application 1 is in third-party application list, and the proof of Register 1 of third-party application 1 is informed to third-party application 1 by Authentication Client.For third-party application 2, third-party application 2 is in third-party application list, and the proof of Register 2 of third-party application 2 is informed to third-party application 2 by Authentication Client.For third-party application 3, third-party application 3 is not in third-party application list, third-party application 3 does not have authority to use the message notice of user rs credentials to third-party application 3 by Authentication Client, being known by third-party application 3 to use this user rs credentials to carry out authentication, and this user rs credentials namely can not be used to access the service server of enterprise.
In the embodiment of the present invention, the proof of Register is specifically as follows and logs in token or Cookie mark.
Third-party application 1, after receiving the proof of Register 1, uses this proof of Register 1 registering service server 1.Service server 1 uses on this proof of Register 1 to aaa server and verifies.If verification succeeds, then service server 1 returns the information logined successfully to third-party application 1, and third-party application 1 can use the business of service server 1.If verify unsuccessfully, then service server 1 returns the information of login failure to third-party application 1, and third-party application 1 cannot use the business of service server 1.
Third-party application 2, after receiving the proof of Register 2, uses this proof of Register 2 registering service server 2.Service server 2 uses on this proof of Register 2 to aaa server and verifies.If verification succeeds, then service server 2 returns the information logined successfully to third-party application 2, and third-party application 2 can use the business of service server 2.If verify unsuccessfully, then service server 2 returns the information of login failure to third-party application 2, and third-party application 2 cannot use the business of service server 2.
Based on technique scheme, in the embodiment of the present invention, for multiple application programs of same enterprise, when the user rs credentials that multiple third-party application is corresponding identical, can carry out authentication for this user rs credentials, multiple application program only needs authentication once, does not need to use this user rs credentials repeatedly to carry out authentication, user-friendly, improve the experience of user.Allow to use user rs credentials to carry out the third-party application of authentication by configuration in third-party application list, which third-party application can be controlled and utilize this user rs credentials to carry out authentication, facilitate the control of authority of third-party application.
Based on the inventive concept same with said method, additionally provide a kind of Authentication Client in the embodiment of the present invention, terminal equipment runs Authentication Client and multiple third-party application, the user rs credentials that described multiple third-party application is corresponding identical, as shown in Figure 4, described Authentication Client specifically comprises:
Authentication module 11, carries out authentication for utilizing described user rs credentials;
Acquisition module 12, for obtaining third-party application list corresponding to described user rs credentials, have recorded the third-party application using described user rs credentials to carry out authentication in described third-party application list;
Judge module 13, after starting at third-party application, if described authentication module authentication success, then judges whether described third-party application is recorded in described third-party application list;
Sending module 14, for when judged result is for being, informs to described third-party application by the proof of Register of third-party application, and described third-party application utilizes the proof of Register to carry out login authentication to service server.
Described authentication module 11, carries out authentication specifically for utilizing in described user rs credentials to aaa server, and receives the authentication success/unsuccessful response message from described aaa server.
Described acquisition module 12, specifically for sending the message for asking the third-party application list using described user rs credentials authority to application authorization server, and receive the response message carrying described third-party application list from described application authorization server; Wherein, described application authorization server is configured with the third-party application list allowing the described user rs credentials of use to carry out the third-party application of authentication.
Described sending module 14, also for after judging whether described third-party application is recorded in described third-party application list, if described third-party application is not recorded in described third-party application list, then do not had by described third-party application authority to use the message notice of described user rs credentials to described third-party application, known by described third-party application and described user rs credentials can not be used to carry out authentication.
In the embodiment of the present invention, described user rs credentials comprises username information and encrypted message, and described the proof of Register is for logging in token or Cookie mark.
Wherein, the modules of apparatus of the present invention can be integrated in one, and also can be separated deployment.Above-mentioned module can merge into a module, also can split into multiple submodule further.
Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the present invention can add required general hardware platform by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better execution mode.Based on such understanding, technical scheme of the present invention can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product is stored in a storage medium, comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform method described in each embodiment of the present invention.It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment, the module in accompanying drawing or flow process might not be that enforcement the present invention is necessary.It will be appreciated by those skilled in the art that the module in the device in embodiment can carry out being distributed in the device of embodiment according to embodiment description, also can carry out respective change and be arranged in the one or more devices being different from the present embodiment.The module of above-described embodiment can merge into a module, also can split into multiple submodule further.The invention described above embodiment sequence number, just to describing, does not represent the quality of embodiment.Be only several specific embodiment of the present invention above, but the present invention is not limited thereto, the changes that any person skilled in the art can think of all should fall into protection scope of the present invention.
Claims (10)
1. unify the method verified, it is characterized in that, terminal equipment runs Authentication Client and multiple third-party application, the user rs credentials that described multiple third-party application is corresponding identical, described method comprises:
Described Authentication Client utilizes described user rs credentials to carry out authentication;
Described Authentication Client obtains third-party application list corresponding to described user rs credentials, have recorded the third-party application using described user rs credentials to carry out authentication in described third-party application list;
After third-party application starts, if described Authentication Client authentication success, then described Authentication Client judges whether described third-party application is recorded in described third-party application list;
If so, the proof of Register of described third-party application is informed to described third-party application by described Authentication Client, is utilized on described the proof of Register to service server carry out login authentication by described third-party application.
2. the method for claim 1, is characterized in that, described Authentication Client utilizes described user rs credentials to carry out the process of authentication, specifically comprises:
Described Authentication Client utilizes in described user rs credentials to authentication and authorization charging aaa server and carries out authentication, and receives the authentication success/unsuccessful response message from described aaa server.
3. the method for claim 1, is characterized in that, described Authentication Client obtains the process of third-party application list corresponding to described user rs credentials, specifically comprises:
Described Authentication Client sends the message for asking the third-party application list using described user rs credentials authority to application authorization server, and receives the response message carrying described third-party application list from described application authorization server; Wherein, described application authorization server is configured with the third-party application list allowing the described user rs credentials of use to carry out the third-party application of authentication.
4. the method for claim 1, is characterized in that, after described Authentication Client judges whether described third-party application is recorded in described third-party application list, described method comprises further:
If described third-party application is not recorded in described third-party application list, then described third-party application does not have authority to use the message notice of described user rs credentials to described third-party application by described Authentication Client, is known described user rs credentials can not be used to carry out authentication by described third-party application.
5. the method as described in any one of claim 1-4, is characterized in that, described user rs credentials specifically comprises username information and encrypted message, and described the proof of Register is specially and logs in token or Cookie mark.
6. an Authentication Client, is characterized in that, terminal equipment runs Authentication Client and multiple third-party application, the user rs credentials that described multiple third-party application is corresponding identical, and described Authentication Client comprises:
Authentication module, carries out authentication for utilizing described user rs credentials;
Acquisition module, for obtaining third-party application list corresponding to described user rs credentials, have recorded the third-party application using described user rs credentials to carry out authentication in described third-party application list;
Judge module, after starting at third-party application, if described authentication module authentication success, then judges whether described third-party application is recorded in described third-party application list;
Sending module, for when judged result is for being, informs to described third-party application by the proof of Register of third-party application, utilizes the proof of Register to carry out login authentication to service server by described third-party application.
7. Authentication Client as claimed in claim 6, it is characterized in that, described authentication module, carries out authentication specifically for utilizing in described user rs credentials to authentication and authorization charging aaa server, and receives the authentication success/unsuccessful response message from described aaa server.
8. Authentication Client as claimed in claim 6, is characterized in that,
Described acquisition module, specifically for sending the message for asking the third-party application list using described user rs credentials authority to application authorization server, and receives the response message carrying described third-party application list from described application authorization server; Wherein, described application authorization server is configured with the third-party application list allowing the described user rs credentials of use to carry out the third-party application of authentication.
9. Authentication Client as claimed in claim 6, is characterized in that,
Described sending module, also for after judging whether described third-party application is recorded in described third-party application list, if described third-party application is not recorded in described third-party application list, then do not had by described third-party application authority to use the message notice of described user rs credentials to described third-party application, known by described third-party application and described user rs credentials can not be used to carry out authentication.
10. the Authentication Client as described in any one of claim 6-9, is characterized in that, described user rs credentials comprises username information and encrypted message, and described the proof of Register is for logging in token or Cookie mark.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510108571.1A CN104753927B (en) | 2015-03-12 | 2015-03-12 | A kind of method and apparatus of unified verification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510108571.1A CN104753927B (en) | 2015-03-12 | 2015-03-12 | A kind of method and apparatus of unified verification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104753927A true CN104753927A (en) | 2015-07-01 |
| CN104753927B CN104753927B (en) | 2018-09-04 |
Family
ID=53593031
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510108571.1A Active CN104753927B (en) | 2015-03-12 | 2015-03-12 | A kind of method and apparatus of unified verification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104753927B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105978688A (en) * | 2016-05-30 | 2016-09-28 | 葛峰 | Information-separation-management-based cross-domain safety authentication method |
| CN110084578A (en) * | 2019-03-27 | 2019-08-02 | 北京三快在线科技有限公司 | Method, apparatus and storage medium based on Third-party payment platform payment |
| TWI768307B (en) * | 2020-03-18 | 2022-06-21 | 傑睿資訊服務股份有限公司 | Open source software integration approach |
| CN115242472A (en) * | 2022-07-08 | 2022-10-25 | 北京新唐思创教育科技有限公司 | An authentication method, device, equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102129287A (en) * | 2011-03-17 | 2011-07-20 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and power supply management method for application program thereof |
| CN102882835A (en) * | 2011-07-13 | 2013-01-16 | 中国科学院声学研究所 | Method and system for implementing single sign on |
| US20140033291A1 (en) * | 2011-04-07 | 2014-01-30 | Tencent Technology (Shenzhen) Company Limited | Method and system for visiting a third party application via a cloud platform |
| CN104065616A (en) * | 2013-03-20 | 2014-09-24 | 中国移动通信集团公司 | Single sign-on method and system |
| CN104301316A (en) * | 2014-10-13 | 2015-01-21 | 中国电子科技集团公司第二十八研究所 | Single sign-on system and implementation method thereof |
-
2015
- 2015-03-12 CN CN201510108571.1A patent/CN104753927B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102129287A (en) * | 2011-03-17 | 2011-07-20 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and power supply management method for application program thereof |
| US20140033291A1 (en) * | 2011-04-07 | 2014-01-30 | Tencent Technology (Shenzhen) Company Limited | Method and system for visiting a third party application via a cloud platform |
| CN102882835A (en) * | 2011-07-13 | 2013-01-16 | 中国科学院声学研究所 | Method and system for implementing single sign on |
| CN104065616A (en) * | 2013-03-20 | 2014-09-24 | 中国移动通信集团公司 | Single sign-on method and system |
| CN104301316A (en) * | 2014-10-13 | 2015-01-21 | 中国电子科技集团公司第二十八研究所 | Single sign-on system and implementation method thereof |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105978688A (en) * | 2016-05-30 | 2016-09-28 | 葛峰 | Information-separation-management-based cross-domain safety authentication method |
| CN105978688B (en) * | 2016-05-30 | 2019-04-16 | 葛峰 | A kind of cross-domain safety certifying method based on information separation management |
| CN110084578A (en) * | 2019-03-27 | 2019-08-02 | 北京三快在线科技有限公司 | Method, apparatus and storage medium based on Third-party payment platform payment |
| TWI768307B (en) * | 2020-03-18 | 2022-06-21 | 傑睿資訊服務股份有限公司 | Open source software integration approach |
| CN115242472A (en) * | 2022-07-08 | 2022-10-25 | 北京新唐思创教育科技有限公司 | An authentication method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104753927B (en) | 2018-09-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10432608B2 (en) | Selectively enabling multi-factor authentication for managed devices | |
| US9083703B2 (en) | Mobile enterprise smartcard authentication | |
| CN107249004B (en) | Identity authentication method, device and client | |
| US9882887B2 (en) | Single sign-on for managed mobile devices | |
| US10305882B2 (en) | Using a service-provider password to simulate F-SSO functionality | |
| CN110730174B (en) | Network access control method, device, equipment and medium | |
| US11057364B2 (en) | Single sign-on for managed mobile devices | |
| CN111131242A (en) | Authority control method, device and system | |
| US20190124073A1 (en) | Single sign-on for managed mobile devices | |
| CN108462710B (en) | Authentication and authorization method, device, authentication server and machine-readable storage medium | |
| US10257188B2 (en) | Offline access control for an application | |
| CN104125565A (en) | Method for realizing terminal authentication based on OMA DM, terminal and server | |
| CN104980926B (en) | The long-range control method and device of mobile terminal | |
| CN106936772A (en) | A kind of access method, the apparatus and system of cloud platform resource | |
| EP3122017B1 (en) | Systems and methods of authenticating and controlling access over customer data | |
| CN105306490A (en) | System, method and device for payment verification | |
| CN111062023B (en) | Method and device for realizing single sign-on of multi-application system | |
| CN109388937B (en) | Single sign-on method and sign-on system for multi-factor identity authentication | |
| CN110519285A (en) | User authen method, device, computer equipment and storage medium | |
| CN105991614A (en) | Open authorization, resource access method and device, and a server | |
| CN108471403A (en) | A kind of method, apparatus, terminal device and the storage medium of account migration | |
| CN105337967B (en) | Realize that user logs in method, system and the central server of destination server | |
| CN106331003A (en) | A method and device for accessing an application portal system on a cloud desktop | |
| CN104753927A (en) | Unified verification method and device | |
| CN117121435A (en) | Connection elastic multi-factor authentication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |