CN109117647B - Authority control management method and management system of mobile application SDK - Google Patents
Authority control management method and management system of mobile application SDK Download PDFInfo
- Publication number
- CN109117647B CN109117647B CN201810782042.3A CN201810782042A CN109117647B CN 109117647 B CN109117647 B CN 109117647B CN 201810782042 A CN201810782042 A CN 201810782042A CN 109117647 B CN109117647 B CN 109117647B
- Authority
- CN
- China
- Prior art keywords
- sdk
- authority
- calling
- identifier
- time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 18
- 238000000034 method Methods 0.000 claims abstract description 32
- 238000012795 verification Methods 0.000 claims abstract description 23
- 230000008569 process Effects 0.000 claims abstract description 9
- 230000000977 initiatory effect Effects 0.000 claims description 9
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 238000001514 detection method Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
Abstract
The invention discloses a permission control management method and a permission control management system for a mobile application SDK (software development kit), which belong to the technical field of computers, and comprise the following steps: judging whether the SDK is used for the first time; judging whether the local has an authentication identifier; if the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt; if the SDK is used for the first time and the authentication identification is not locally available, calling the SDK; if the SDK is not used for the first time and the local authority identification is available, the SDK is called; if the SDK is not used for the first time and the right checking mark is not locally available, whether the number of times of exempting the right is exceeded is judged. In the method disclosed by the invention, for the third-party application which is not applied or is applied in the application process, the SDK can be used for function development and verification, the number of times for calling the SDK is limited, and an applicant cannot issue the SDK, so that the requirement of rapid development can be met, and the requirement of authority management for calling the SDK can be met.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a permission control management method and a permission control management system for a mobile application SDK.
Background
The mobile terminal SDK is issued by an organization or an individual, and can be used by a third party application to package a software package or a software library with specific functions. For developers or development organizations of the SDK, after the SDK is released and spread and circulated over the internet, how to control versions and rights of third-party applications using the SDK is a troublesome problem, and the following problems may occur:
1. the right verification is completely localized and is easier to be cracked reversely, multiple SDKs must be generated according to different applications, and the right recovery cannot be realized after the third-party application right is expired.
2. The right of verification completely depends on a white list of a cloud, so that network access must be performed every time or for the first time to determine whether the third-party application has the right to use the SDK, the user experience is difficult to guarantee under the condition that the network condition is not good enough, and corresponding delay exists even if the network condition is good.
3. If the SDK must be verified before it can be used, it is not friendly enough for the developer of the third party application. The third-party application developer can perform development verification after applying for the right, and the development time of the third-party application publisher is delayed in the process.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a method and a system for controlling and managing an authority of a mobile application SDK. The technical scheme is as follows:
in one aspect, the present invention provides a method for controlling and managing the authority of a mobile application SDK, which comprises the following main steps:
judging whether the SDK is used for the first time;
judging whether the local has an authentication identifier;
if the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt;
if the SDK is used for the first time and the authentication identification is not locally available, calling the SDK;
if the SDK is not used for the first time and the local authority identification is available, the SDK is called;
if the SDK is not used for the first time and the right checking mark is not locally available, whether the number of times of exempting the right is exceeded is judged.
With reference to the first aspect, in a first possible implementation manner, the determining is performed to determine whether the number of times of exempting from the authority is exceeded, and if the number of times of exempting from the authority is not exceeded, the SDK is called;
if the number of times of exempting from the authority exceeds, initiating synchronous network connection, judging whether the authority for calling the SDK exists, and if the authority for calling the SDK exists, generating an authority verification identifier and calling the SDK; if the authority of calling the SDK is not available, the SDK calling is failed.
With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner, if the number of times of invoking the SDK does not exceed the number of times of exempting from the authority, if there is network connection, initiating asynchronous network authentication, determining whether there is authority to invoke the SDK, and if there is authority to invoke the SDK, generating an authentication identifier and invoking the SDK; and if the SDK authority is not called, the SDK calling is failed.
With reference to any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner, if the SDK is not used for the first time and the local authentication identifier is available, in a process of invoking the SDK, if there is network connection, initiating asynchronous network authentication, and determining whether there is an authority to continue using the SDK; if the SDK authority is not used continuously, clearing the authority checking identifier; and if the SDK is allowed to be used continuously, calling the SDK.
With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, the method for generating the right-checking identifier includes the following steps:
generating a device fingerprint, and acquiring an authentication identifier and an SDK version number;
assembling the device fingerprint, the authentication identification and the SDK version number into a first character string;
performing sha3 algorithm operation on the first character string to generate a first hash;
generating a private key locally and randomly, and calculating a first public key through an elliptic curve algorithm according to the private key;
generating a digital signature by the first hash and a private key;
and checking the digital signature, wherein if the checking is successful, the digital signature is the authentication identifier.
With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, the authentication identifier refers to a unique identifier that is assigned by the cloud according to a name identifier filled by a client.
With reference to the fifth or sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, the verifying the digital signature includes the following steps:
uploading the digital signature, the device fingerprint, the SDK version number and the first public key to a cloud end;
the cloud end assembles a second character string according to the pre-registered authentication identification white list, the transmitted device fingerprint and the SDK version number;
the second character string is operated through the sha3 algorithm to generate a second hash;
the cloud end calculates a second public key through an elliptic curve algorithm according to the second hash and the digital signature;
and comparing the first public key with the second public key, wherein if the comparison is consistent, the digital signature is an authentication identifier.
In another aspect, the present invention provides a system for controlling and managing permissions of a mobile application SDK, the system comprising: a third party application, an SDK, a cloud server;
the third party application comprises: calling an SDK interface for calling the SDK;
the SDK includes: the external interface is connected with the calling SDK interface;
the authority control module is connected with the external interface;
the SDK function module is connected with the authority control module and the external interface module;
the cloud server includes: and the network interface is connected with the authority control module.
With reference to the second aspect, in a second possible implementation manner, the authority control module includes: the first-time authority control module and the non-first-time authority control module; the non-primary permission control module comprises: the system comprises an authority-free times verification module, an authority-free times exceeding control module and an authority-free times not exceeding control module.
With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner, the first permission control module includes: the verification identification detection module and the alarm prompt module; the number of times of exceeding the exemption authority and the number of times of not exceeding the exemption authority both include: the device comprises a network detection module and a verification identification generation module.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
1. for the third-party application which is not applied or is applied in the application flow, the method disclosed by the invention can also use the SDK to carry out function development and verification, and has the limitation of times for calling the SDK, so that an applicant cannot issue the SDK, on one hand, the requirement of rapid development can be met, and on the other hand, the requirement of authority management for calling the SDK is met;
2. according to the method disclosed by the invention, when the permission applied by the third party is overdue, the use permission can be closed in time;
3. under the condition that the network condition is not good enough, the invention can still ensure the SDK use of the user, and can not cause bad influence on the use experience of the user;
4. the SDK data verification in the method disclosed by the invention adopts an elliptic curve algorithm, so that the unsafe problem that the public key is easily leaked by the client side because the public key is directly exposed to the client side after the public key is generated by the server side in the traditional RSA algorithm is avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of an authority control management method for a mobile application SDK according to embodiment 1 of the present invention;
fig. 2 is a flowchart of a verification identification generation method provided in embodiment 1 of the present invention;
fig. 3 is a flowchart of a method for verifying a digital signature according to embodiment 1 of the present invention;
fig. 4 is a flowchart of an authority control management method for a mobile application SDK according to embodiment 2 of the present invention;
fig. 5 is a schematic diagram of an authority control management system of a mobile application SDK according to embodiment 3 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
As shown in fig. 1, a method for controlling and managing the authority of a mobile application SDK includes the following steps:
s01: judging whether the SDK is used for the first time;
s02: judging whether the local has an authentication identifier;
the above determination yields the following four results:
1. if the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt;
2. if the SDK is used for the first time and the authentication identification is not locally available, calling the SDK;
3. if the SDK is not used for the first time and the local authority identification is available, the SDK is called;
4. if the SDK is not used for the first time and the right checking mark is not locally available, whether the number of times of exempting the right is exceeded is judged.
Wherein, the judgment related in the 4 th result is whether the number of times of the permission exemption is exceeded, and the following two results are generated:
1. if the number of times of exempting authority is not exceeded, calling the SDK;
2. if the number of times of exempting from the authority exceeds, initiating synchronous network connection, judging whether the authority for calling the SDK exists, and if the authority for calling the SDK exists, generating an authority verification identifier and calling the SDK; if the authority of calling the SDK is not available, the SDK calling is failed.
As shown in fig. 2, in the 2 nd result generated by judging whether the number of times of exemption is exceeded, the generation method of the involved authentication identifier includes the following steps:
generating a device fingerprint, and acquiring an authentication identifier and an SDK version number;
assembling the device fingerprint, the authentication identification and the SDK version number into a first character string;
performing sha3 algorithm operation on the first character string to generate a first hash;
generating a private key locally and randomly, and calculating a first public key through an elliptic curve algorithm according to the private key;
generating a digital signature by the first hash and a private key;
and checking the digital signature, wherein if the checking is successful, the digital signature is the authentication identifier.
In the verification identification generation method, the authentication identification refers to a unique identification distributed by the cloud according to the name identification filled by the client.
As shown in fig. 3, in the verification identification generation method, verifying the digital signature includes the following steps:
uploading the digital signature, the device fingerprint, the SDK version number and the first public key to a cloud end;
the cloud end assembles a second character string according to the pre-registered authentication identification white list, the transmitted device fingerprint and the SDK version number;
the second character string is operated through the sha3 algorithm to generate a second hash;
the cloud end calculates a second public key through an elliptic curve algorithm according to the second hash and the digital signature;
and comparing the first public key with the second public key, wherein if the comparison is consistent, the digital signature is an authentication identifier.
Example 2
As shown in fig. 4, a method for controlling and managing the authority of a mobile application SDK includes the following steps:
s01: judging whether the SDK is used for the first time;
s02: judging whether the local has an authentication identifier;
the above determination yields the following four results:
1. if the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt;
2. if the SDK is used for the first time and the authentication identification is not locally available, calling the SDK;
3. if the SDK is not used for the first time and the local authority identification is available, calling the SDK, judging whether network connection exists locally while calling the SDK, if so, initiating asynchronous network authentication, and judging whether the SDK is allowed to be used continuously; if the SDK authority is not used continuously, clearing the authority checking identifier; if the permission of continuing using the SDK exists, calling the SDK;
4. if the SDK is not used for the first time and the right checking mark is not locally available, whether the number of times of exempting the right is exceeded is judged.
Wherein, the judgment related in the 4 th result is whether the number of times of the permission exemption is exceeded, and the following two results are generated:
1. if the number of times of the exempting permission is not exceeded, calling the SDK, judging whether network connection exists locally in the process of calling the SDK, if so, initiating asynchronous network connection, judging whether the permission of calling the SDK exists, and if so, generating a verification identifier and calling the SDK; if the SDK authority is not called, the SDK calling is failed;
2. if the number of times of exempting from the authority exceeds, initiating synchronous network authentication, judging whether the authority of calling the SDK exists, and if the authority of calling the SDK exists, generating an authentication identifier and calling the SDK; if the authority of calling the SDK is not available, the SDK calling is failed.
As shown in fig. 2, in the 2 nd result generated by judging whether the number of times of exemption is exceeded, the generation method of the involved authentication identifier includes the following steps:
generating a device fingerprint, and acquiring an authentication identifier and an SDK version number;
assembling the device fingerprint, the authentication identification and the SDK version number into a first character string;
performing sha3 algorithm operation on the first character string to generate a first hash;
generating a private key locally and randomly, and calculating a first public key through an elliptic curve algorithm according to the private key;
generating a digital signature by the first hash and a private key;
and checking the digital signature, wherein if the checking is successful, the digital signature is the authentication identifier.
In the verification identification generation method, the authentication identification refers to a unique identification distributed by the cloud according to the name identification filled by the client.
As shown in fig. 3, in the verification identification generation method, verifying the digital signature includes the following steps:
uploading the digital signature, the device fingerprint, the SDK version number and the first public key to a cloud end;
the cloud end assembles a second character string according to the pre-registered authentication identification white list, the transmitted device fingerprint and the SDK version number;
the second character string is operated through the sha3 algorithm to generate a second hash;
the cloud end calculates a second public key through an elliptic curve algorithm according to the second hash and the digital signature;
and comparing the first public key with the second public key, wherein if the comparison is consistent, the digital signature is an authentication identifier.
This embodiment has two different points compared with embodiment 1:
1. in the process of calling the SDK under the condition that the authentication identifier is not firstly and locally provided, a network authentication step is added, and the method mainly aims to judge whether a user has the right of logging in again and set or clear the authentication identifier according to the judgment result.
2. The method is mainly used for generating the authentication identifier for networking in the process of calling the SDK under the condition that the SDK is not used for the first time, the authentication identifier is not locally generated and the number of times of exempting authority is not exceeded, so that the authentication identifier is not required to be set again in the next login process, and the condition that the SDK cannot be logged in due to no network connection in the next login process is avoided.
Based on the above two different points, embodiment 2 has the advantage that the SDK can still be logged in without a local network, thereby ensuring good login experience of the user.
Example 3
As shown in fig. 5, the present invention provides an authority control management system for a mobile application SDK based on embodiment 2, and the system includes: a third party application, an SDK, a cloud server;
the third party application comprises: calling an SDK interface for calling the SDK;
the SDK includes: the external interface is connected with the calling SDK interface;
the authority control module is used for being connected with the external interface;
the SDK function module is used for being connected with the authority control module and the external interface module;
the cloud server includes: and the network interface is connected with the authority control module.
Further, the right control module comprises: the first-time authority control module and the non-first-time authority control module; the non-primary permission control module comprises: the system comprises an authority-free times verification module, an authority-free times exceeding control module and an authority-free times not exceeding control module.
Further, the first-time authority control module comprises: the verification identification detection module and the alarm prompt module; the number of times of exceeding the exemption authority and the number of times of not exceeding the exemption authority both include: the device comprises a network detection module and a verification identification generation module.
All the above-mentioned optional technical solutions can be combined arbitrarily to form the optional embodiments of the present invention, and are not described herein again.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (7)
1. A permission control management method of a mobile application SDK is characterized by comprising the following main steps:
judging whether the SDK is used for the first time;
judging whether the local has an authentication identifier;
if the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt;
if the SDK is used for the first time and the authentication identification is not locally available, calling the SDK;
if the SDK is not used for the first time and the local authority checking identifier exists, calling the SDK, judging whether network connection exists locally while calling the SDK, if so, initiating asynchronous network authority checking, judging whether the authority of continuously using the SDK exists, and if so, directly calling the SDK when the SDK is used again;
if the SDK is not used for the first time and the right checking mark is not locally available, judging whether the number of times of exempting the right is exceeded or not;
the generation of the right-checking identifier comprises the following steps: generating an equipment fingerprint, acquiring an authentication identifier and an SDK version number, assembling the equipment fingerprint, the authentication identifier and the SDK version number into a first character string, operating the first character string through a sha3 algorithm to generate a first hash, locally and randomly generating a private key, calculating a first public key through an elliptic curve algorithm according to the private key, generating a digital signature through the first hash and the private key, checking the digital signature, and if the check is successful, taking the digital signature as a verification identifier.
2. The method as claimed in claim 1, wherein the determining step determines whether the number of times of exemption is exceeded, and if not, calls the SDK;
if the number of times of exempting from the authority exceeds, initiating synchronous network connection, judging whether the authority for calling the SDK exists, and if the authority for calling the SDK exists, generating an authority verification identifier and calling the SDK; if the authority of calling the SDK is not available, the SDK calling is failed.
3. The authority control management method of the mobile application SDK according to claim 2, wherein if the number of times of exempting authority is not exceeded, in the process of calling the SDK, if there is network connection, asynchronous network authentication is initiated, whether there is authority to call the SDK is judged, if there is authority to call the SDK, an authority verification identifier is generated, and the SDK is directly called when used again; and if the SDK authority is not called, the SDK calling is failed.
4. The method as claimed in any one of claims 1 to 3, wherein if the SDK is not used for the first time and the local authority check identifier exists, the SDK is called, and the SDK is called while determining whether there is a local network connection, if there is a network connection, an asynchronous network authentication is initiated, and if the SDK authority is not used continuously, the authority check identifier is cleared.
5. The method as claimed in claim 1, wherein the authentication identifier is a unique identifier assigned by the cloud according to a name identifier filled by the client.
6. A method for rights control management of a mobile application SDK according to any of the claims 1, wherein said verifying the digital signature comprises the steps of:
uploading the digital signature, the device fingerprint, the SDK version number and the first public key to a cloud end;
the cloud end assembles a second character string according to the pre-registered authentication identification white list, the transmitted device fingerprint and the SDK version number;
the second character string is operated through the sha3 algorithm to generate a second hash;
the cloud end calculates a second public key through an elliptic curve algorithm according to the second hash and the digital signature;
and comparing the first public key with the second public key, wherein if the comparison is consistent, the digital signature is an authentication identifier.
7. An authority control management system of a mobile application (SDK), comprising: a third party application, an SDK, a cloud server;
the third party application comprises: calling an SDK interface for calling the SDK;
the SDK includes: the external interface is connected with the calling SDK interface;
the authority control module is connected with the external interface and used for judging whether the SDK is used for the first time or not, judging whether the local authority identification exists or not, judging whether the use times exceed the authority-free times or not, and determining whether the SDK is allowed to be called according to the judgment result, wherein the authority control module comprises:
when the SDK is used for the first time and the local authority identification is available, calling an interface to send an alarm prompt;
when the SDK is used for the first time and the authentication identification is not locally available, the SDK is called;
when the SDK is not used for the first time and the local authority identification exists, the SDK is called, whether network connection exists in the local is judged while the SDK is called, if the network connection exists, asynchronous network authority is initiated, whether the authority for continuously using the SDK exists is judged, and if the authority exists, the SDK is directly called when the SDK is used again;
when the SDK is not used for the first time and the authentication identification is not locally available, judging whether the number of times of exempting the authority is exceeded or not;
the SDK function module is connected with the authority control module and the external interface module;
the cloud server includes: the network interface is connected with the authority control module;
the generation of the right-checking identifier comprises the following steps: generating an equipment fingerprint, acquiring an authentication identifier and an SDK version number, assembling the equipment fingerprint, the authentication identifier and the SDK version number into a first character string, operating the first character string through a sha3 algorithm to generate a first hash, locally and randomly generating a private key, calculating a first public key through an elliptic curve algorithm according to the private key, generating a digital signature through the first hash and the private key, checking the digital signature, and if the check is successful, taking the digital signature as a verification identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810782042.3A CN109117647B (en) | 2018-07-17 | 2018-07-17 | Authority control management method and management system of mobile application SDK |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810782042.3A CN109117647B (en) | 2018-07-17 | 2018-07-17 | Authority control management method and management system of mobile application SDK |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109117647A CN109117647A (en) | 2019-01-01 |
| CN109117647B true CN109117647B (en) | 2021-03-02 |
Family
ID=64862757
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810782042.3A Active CN109117647B (en) | 2018-07-17 | 2018-07-17 | Authority control management method and management system of mobile application SDK |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109117647B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112528248A (en) * | 2020-12-08 | 2021-03-19 | 北京航天云路有限公司 | User authority management scheme facing multiple applications |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102034059A (en) * | 2010-12-02 | 2011-04-27 | 东莞宇龙通信科技有限公司 | Method and device for managing application program and terminal |
| CN103167498A (en) * | 2011-12-19 | 2013-06-19 | 卓望数码技术（深圳）有限公司 | Ability control method and system |
| CN106709280A (en) * | 2016-12-08 | 2017-05-24 | 北京旷视科技有限公司 | Method, client and server for processing information |
| CN107070948A (en) * | 2017-05-23 | 2017-08-18 | 广东工业大学 | Signature and verification method based on hybrid encryption algorithm in cloud storage |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5599557B2 (en) * | 2008-08-29 | 2014-10-01 | 株式会社リコー | Information processing apparatus, license determination method, program, and recording medium |
| CN104426948A (en) * | 2013-08-28 | 2015-03-18 | 北京闹米科技有限公司 | Network data sharing system and network data sharing method |
| WO2015062494A1 (en) * | 2013-10-29 | 2015-05-07 | 北京奇虎科技有限公司 | Method and device for sdk uploading and downloading of a file |
| CN103617394A (en) * | 2013-12-04 | 2014-03-05 | 北京网秦天下科技有限公司 | SDK providing and invoking method and associated device |
| CN103793633A (en) * | 2014-02-14 | 2014-05-14 | 宇龙计算机通信科技(深圳)有限公司 | Method and device for calibrating SDK |
| CN104836784B (en) * | 2014-09-25 | 2018-05-15 | 腾讯科技（北京）有限公司 | A kind of information processing method, client and server |
| CN106295310A (en) * | 2016-07-28 | 2017-01-04 | 乐视控股（北京）有限公司 | Third party's program SDK authentication processing method and device |
| CN107689870B (en) * | 2017-08-29 | 2021-02-02 | 杭州绿湾网络科技有限公司 | Client authentication method and system |
| CN107704334A (en) * | 2017-10-13 | 2018-02-16 | 维沃移动通信有限公司 | A kind of SDK processing method and mobile terminal |
-
2018
- 2018-07-17 CN CN201810782042.3A patent/CN109117647B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102034059A (en) * | 2010-12-02 | 2011-04-27 | 东莞宇龙通信科技有限公司 | Method and device for managing application program and terminal |
| CN103167498A (en) * | 2011-12-19 | 2013-06-19 | 卓望数码技术（深圳）有限公司 | Ability control method and system |
| CN106709280A (en) * | 2016-12-08 | 2017-05-24 | 北京旷视科技有限公司 | Method, client and server for processing information |
| CN107070948A (en) * | 2017-05-23 | 2017-08-18 | 广东工业大学 | Signature and verification method based on hybrid encryption algorithm in cloud storage |
Non-Patent Citations (1)
| Title |
|---|
| 区块链技术：架构及进展;邵奇峰 等;《计算机学报》;20180531;第41卷(第5期);第981页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109117647A (en) | 2019-01-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3061027B1 (en) | Verifying the security of a remote server | |
| US9053306B2 (en) | Authentication system, authentication server, service providing server, authentication method, and computer-readable recording medium | |
| CN111355726B (en) | Identity authorization login method and device, electronic equipment and storage medium | |
| CN112671720B (en) | Token construction method, device and equipment for cloud platform resource access control | |
| CN105306534A (en) | Information verification method based on open platform and open platform | |
| CN109995776B (en) | Internet data verification method and system | |
| US20180365045A1 (en) | Virtual machine integrity | |
| CN104753674A (en) | Application identity authentication method and device | |
| CN110912689A (en) | Method and system for generating and verifying unique value | |
| WO2019178763A1 (en) | Certificate importing method and terminal | |
| CN105279404B (en) | Operating system method of controlling operation thereof and device | |
| CN107645474B (en) | Method and device for logging in open platform | |
| CN109117647B (en) | Authority control management method and management system of mobile application SDK | |
| CN110166471A (en) | A kind of portal authentication method and device | |
| CN104092733B (en) | A kind of credible distributed file system based on HDFS | |
| CN110602051B (en) | Information processing method based on consensus protocol and related device | |
| CN109818915B (en) | Information processing method and device, server and readable storage medium | |
| CN110581833B (en) | Service security protection method and device | |
| CN110890979A (en) | Automatic deploying method, device, equipment and medium for fortress machine | |
| CN110581863B (en) | Single sign-on method, device, equipment and medium for cloud platform | |
| CN113965342A (en) | Trusted network connection system and method based on domestic platform | |
| CN115021995B (en) | Multi-channel login method, device, equipment and storage medium | |
| CN113271306B (en) | Data request and transmission method, device and system | |
| CN114978626B (en) | Trusted computing method, device, equipment and medium based on block chain | |
| CN110881047A (en) | Safe and reliable third party authentication scheme |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240306 Address after: Room 1179, W Zone, 11th Floor, Building 1, No. 158 Shuanglian Road, Qingpu District, Shanghai, 201702 Patentee after: Shanghai Zhongan Information Technology Service Co.,Ltd. Country or region after: China Address before: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Patentee before: ZHONGAN INFORMATION TECHNOLOGY SERVICE Co.,Ltd. Country or region before: China |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20240415 Address after: Room 1179, W Zone, 11th Floor, Building 1, No. 158 Shuanglian Road, Qingpu District, Shanghai, 201702 Patentee after: Shanghai Zhongan Information Technology Service Co.,Ltd. Country or region after: China Address before: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Patentee before: ZHONGAN INFORMATION TECHNOLOGY SERVICE Co.,Ltd. Country or region before: China |