CN108830099A - Call verification method, device, computer equipment and the storage medium of api interface - Google Patents
Call verification method, device, computer equipment and the storage medium of api interface Download PDFInfo
- Publication number
- CN108830099A CN108830099A CN201810421551.3A CN201810421551A CN108830099A CN 108830099 A CN108830099 A CN 108830099A CN 201810421551 A CN201810421551 A CN 201810421551A CN 108830099 A CN108830099 A CN 108830099A
- Authority
- CN
- China
- Prior art keywords
- application end
- party application
- user
- data
- api interface
- 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.)
- Pending
Links
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/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Storage Device Security (AREA)
- Computer And Data Communications (AREA)
Abstract
A kind of verification method, device, computer equipment and storage medium for calling api interface provided herein, server receive call request of the third-party application end to api interface, the characteristic information at third-party application end are carried in the call request；According to the call request, the characteristic information for issuing one and the third-party application end establishes the first interim token of binding relationship to the third-party application end；Receive the request of data that user is sent by the third-party application end；Authority Verification is carried out to the request of data；According to verification result, call request of the third-party application end to the api interface is handled.The application input without user the operation of password, while needing to verify the much information in request of data, enhances the data safety of user's access, simplifies user's operation, overcomes and calls api interface cumbersome at present and the unsafe defect of calling.
Description
Technical field
This application involves Internet technical field, in particular to a kind of verification method, device, calculating for calling api interface
Machine equipment and storage medium.
Background technique
Requesting party (user) logs in third-party application end (any application end), it is often desirable to access on third-party application
Others application, at this point, can then pass through api interface (the Application Programming of calling other application
Interface, application programming interface) it accesses.
Api interface, which is mainly available to when applications end (third-party application end) is called, to be used, i.e., user has stepped at it
It is wanted access on the applications end of record other in application, by calling the api interface of other application to realize.At present in the industry
The mode for calling api interface is mostly that the modes such as user password certification login, simple token (interim token) are realized.
The cipher authentication login mode of user password needs user to input password or saves password, cumbersome dangerous.
And the wind that user although may be implemented using simple token mode and exempt from password login, but be crawled or reveal there are token
Danger.
There are no mature cross-platform SSO across languages, (Single Sign On, single-point are stepped in Django frame at present
Record) scheme.Meanwhile existing authentication mode can not dock very well third-party application permission control carry out unified permission pipe
Reason.
Summary of the invention
The main purpose of the application is to provide a kind of verification method, device, computer equipment and storage for calling api interface
Medium overcomes and calls api interface cumbersome at present and the unsafe defect of calling.
To achieve the above object, this application provides a kind of verification method for calling api interface, include the following steps：
Server receives call request of the third-party application end to api interface, carries third party in the call request
The characteristic information of application end, the characteristic information are the ID and password at the preset third-party application end for having and calling permission；
According to the call request, a first interim token is issued to the third-party application end, wherein described first
Interim token is the interim token that binding relationship is established with the characteristic information at the third-party application end；
The request of data that user is sent by the third-party application end is received, it is interim to carry second in the request of data
Token and the user information for logging in the third-party application end subscriber；
When the described first interim token is identical as the described second interim token, permission is carried out to the user information and is tested
Card；
According to verification result, call request of the third-party application end to the api interface is handled.
Further, described according to verification result, handle call request of the third-party application end to the api interface
The step of, including：
Call request if being verified, by the third-party application end to the api interface；If verifying obstructed
It crosses, then feedback includes the verification result of abnormal cause to the third-party application end.
Further, the user information includes user type and user account information, described to the user information
Carry out Authority Verification the step of include：
Successively the user type and user account information are verified, to verify whether the user has access
Permission.
It further, further include the IP address information at the third-party application end in the request of data.
Further, before described the step of carrying out Authority Verification to the user information, including：
According to the IP address information at the third-party application end, verify whether within the scope of authority.
Further, the call request if described be verified, by the third-party application end to the api interface
The step of after, including：
The requested page of data of the request of data is shown on the third-party application end.
Further, described that the requested page of data of the request of data is shown on the third-party application end
Step, including：
The content of pages in the page of data is extracted, and obtains the page layout at the third-party application end；
The content of pages of extraction is distributed according to the page layout at the third-party application end, and will be after distribution
Content of pages be shown on the third-party application end.
Present invention also provides a kind of verifying devices for calling api interface, including：
First receiving unit is taken in the call request for receiving call request of the third-party application end to api interface
Characteristic information with third-party application end, the characteristic information are the ID at the preset third-party application end for having and calling permission
And password；
Issuance unit, for according to the call request, issuing a first interim token to the third-party application end,
Wherein, the described first interim token is the first interim order that binding relationship is established with the characteristic information at the third-party application end
Board；
Second receiving unit, the request of data sent for receiving user by the third-party application end, the data
The second interim token is carried in request and logs in the user information of the third-party application end subscriber；
Authentication unit, for when the described first interim token is identical as the described second interim token, to user letter
Breath carries out Authority Verification；
Processing unit, for handling the third-party application end and being asked to the calling of the api interface according to verification result
It asks.
The application also provides a kind of computer equipment, including memory and processor, is stored with calculating in the memory
The step of machine program, the processor realizes any of the above-described the method when executing the computer program.
The application also provides a kind of computer storage medium, is stored thereon with computer program, the computer program quilt
The step of processor realizes method described in any of the above embodiments when executing.
Verification method, device, computer equipment and the storage medium of calling api interface provided herein, have with
Lower beneficial effect：
Verification method, device, computer equipment and the storage medium of calling api interface provided herein, receive
When third-party application end is to the call request of api interface, the characteristic information foundation for issuing one and the third-party application end is tied up
The first interim token of relationship is determined to the third-party application end, the unique mark of the first interim token as third-party application end
Know, user data is caused unsafe risk occur when avoiding being stolen；The operation of input password is carried out without user, is needed simultaneously
Much information in request of data verified, enhance the data safety of user's access, simplified user's operation, overcome mesh
Preceding calling api interface is cumbersome and calls unsafe defect.
Detailed description of the invention
Fig. 1 is the verification method step schematic diagram that api interface is called in one embodiment of the application；
Fig. 2 is the verification method step schematic diagram that api interface is called in another embodiment of the application；
Fig. 3 is the verifying apparatus structure block diagram that api interface is called in one embodiment of the application；
Fig. 4 is processing unit structural block diagram in one embodiment of the application；
Fig. 5 is authentication unit structural block diagram in one embodiment of the application；
Fig. 6 is authentication unit structural block diagram in another embodiment of the application；
Fig. 7 is the structural schematic block diagram of the computer equipment of one embodiment of the application.
The embodiments will be further described with reference to the accompanying drawings for realization, functional characteristics and the advantage of the application purpose.
Specific embodiment
It is with reference to the accompanying drawings and embodiments, right in order to which the objects, technical solutions and advantages of the application are more clearly understood
The application is further elaborated.It should be appreciated that specific embodiment described herein is only used to explain the application, not
For limiting the application.
Referring to Fig.1, a kind of verification method for calling api interface is provided in the embodiment of the present application, is included the following steps：
Step S1, server receive call request of the third-party application end to api interface, carry in the call request
The characteristic information at third-party application end；The characteristic information include it is preset have call permission third-party application end ID and
Its corresponding password only can also identify whether the third-party application end has calling permission by ID, and combining cipher facilitates
Safety is promoted, is counterfeited when ID being avoided to be stolen.It is preset on server in the present embodiment with the third for calling permission
The list of the ID of square application end and its corresponding password.
In the present embodiment, each third-party application end all has the characteristic information of own, such as ID, password, close
Key etc. is used to indicate the uniqueness at each third-party application end.User (requesting party of data access) is stepped on by account, password
Record above-mentioned third-party application end, and want to open its data application end wanted access on third-party application end, with access its
Data on the data application end, while being not desired to log in above-mentioned data application end again, then need to call the API at the data application end
Interface.In general, the access information (such as icon etc.) at above-mentioned data application end can be set on the third-party application end, use
Family click access information then automatic trigger third-party application end call data application end api interface call request, the calling
It further include the ID for having third-party application end in request.Above-mentioned server is the management server at above-mentioned data application end, can be connect
Receive call request of the above-mentioned third-party application end to api interface.Above-mentioned data application end is any application end, ground of illustrating, this
For data application end group in embodiment in Django frame, Django is the Web application framework an of open source code, by
Python is write as.The data application end introduces oauth2 standard, can permit user in the standard and allows third-party application is disconnected to visit
Resource (such as photo, video, contacts list etc.) of the user on data application end is asked, without by username and password
It is supplied to data application end, purpose is exactly not need input user password to log in the money that he can be accessed under system permission
Source facilitates user to access, and promotes user experience and access efficiency.
Step S2 issues a first interim token to the third-party application end according to the call request, wherein
The first interim token is the interim token that binding relationship is established with the characteristic information at the third-party application end.
In the present embodiment, after server receives above-mentioned third-party application end to the call request of api interface, therefrom obtain
To the ID and password at third-party application end, verify its for it is preset have call permission third-party application end when, according to the ID
A first interim token (token) is generated, the ID at the first interim token and third-party application end is established into binding relationship, on
The validity for stating the first interim token has time limit regular hour, such as one minute, half an hour.In other embodiments, it is
The safety that api interface is called at third-party application end is further strengthened, key can also be got from features described above information
Information (has uniqueness), generates the interim order with binding relationship according to the key at third-party application end and ID are corresponding
Board.The above-mentioned first interim token can be stolen to avoid other third-party application ends, be palmed off by modifying its ID to steal
Data.
Step S3 receives the request of data that user is sent by the third-party application end, carries in the request of data
Second interim token and the user information for logging in the third-party application end subscriber.
It, then will be above-mentioned when third-party application termination receives the first interim token that above-mentioned server issues in the present embodiment
Unique identification of the first interim token as parameter value as third-party application end, while user passes through the third-party application end
Send request of data, include in the request of data user want access to data information (operation that user needs to carry out or
The data gone for), the user information of user, interim token, the characteristic information at third-party application end etc..
When user logs on to third-party application end, which will record user information (user name etc.), when with
User information can be sent to server by the third-party application end when api interface is called by third-party application end in family.According to
Family information can be which third-party application end to call api interface by with identity user, according to the ID at third-party application end with
And user type may determine that whether the user is user in permission.According to the above-mentioned second interim token and the first interim token
It is whether identical, it can be determined that the third-party application end whether be above-mentioned calling api interface application end, avoid being counterfeited.
Step S4 carries out the user information when the described first interim token is identical as the described second interim token
Authority Verification.
Due to carrying the data information of access in need in above-mentioned request of data, the permission of above-mentioned user information is tested
After card, user then can directly be accessed, without issuing data information again.The Authority Verification of this step is exactly to realize not
User is needed to input the content that user password can be directly accessed within the scope of user right in data application end again, i.e.,
Close login is exempted from realization.
In this step, it after server gets above-mentioned request of data, in order to reinforce safety, needs to ask above-mentioned data
Each single item in asking carries out Authority Verification.For example, can first verify whether above-mentioned third-party application end is to initiate that api interface is called to ask
The application end asked, then above-mentioned user type is checked inside preset permission system and whether data application end matches, and check
Whether the user has corresponding operation permission.Judge that the third-party application end whether data application end allows requesting party to log in is come
Data application end is called, and judges whether the user has the permission of access data application end according to user name.In the present embodiment,
It is verified for each single item information in request of data, multiple-authentication, enhances safety, user data is avoided to be stolen.
Step S5 handles call request of the third-party application end to the api interface according to verification result.This reality
It applies in example, after server is to the Authority Verification of above-mentioned user information, processing can be respectively corresponded according to verification result.
In above process, user is not needed always and carries out corresponding register, and server can be to the access right of user
Limit is verified automatically, simplifies the operation of user；And authentication mechanism when above-mentioned calling api interface has ensured the peace of user data
Quan Xing.
Specifically, above-mentioned according to verification result, handle call request of the third-party application end to the api interface
Step S5, including：
S51, the call request if being verified, by the third-party application end to the api interface；
S52, if verifying does not pass through, feedback includes the verification result of abnormal cause to the third-party application end.
In the present embodiment, it if the Authority Verification of above-mentioned request of data all passes through, by above-mentioned call request and returns
Processing result is returned, i.e., permission user accesses its function of wanting access to, and obtains corresponding data.If in above-mentioned request of data
The failure of any one Authority Verification, verifying do not pass through, and return to verification result, include in verification result verifying can not by it is specific
Abnormal cause, such as user do not have corresponding authority, third-party application end lack of competence etc..
In one embodiment, before the above-mentioned step S4 for carrying out Authority Verification to the user information, including：
S4a, verifies the first interim token and whether the described second interim token is identical.
As described in above-mentioned steps S2, the binding relationship for having the first interim token and third-party application end, this step are established
In be then verifying to third-party application end, if in this step, above-mentioned first interim token and the second interim token be not corresponding,
It then may determine that the third-party application end is then judged to verifying in the presence of the possibility for stealing data in order to ensure secure user data
Do not pass through.
In one embodiment, above-mentioned user information includes user type and user account information, described to the user
Information carries out the step of Authority Verification, including：
Successively the user type and user account information are verified, to verify whether the user has access
Permission.
In the present embodiment, if above-mentioned steps S4a is verified, continue to verify whether the user has access authority, have
Body can first judge whether user type meets the requirements, if meeting the requirements, then judge whether user account information meets the requirements.Into
One step, the access authority whether user has the application can be not only verified, can also further judge what it was specifically accessed
Whether module has corresponding permission.For example, the data application end in the present embodiment has multiple modules, different modules is not to
Same user group is open, therefore not only needs to verify the permission whether user has access data application end, it is also necessary to verify
Whether it has the permission for accessing some module.
It in one embodiment, further include the IP address letter at the third-party application end in the request of data in above-mentioned steps S3
Breath.Third application end then can together upload IP address information when sending request of data, can also to IP in the present embodiment
The permission of location information is verified.
In the present embodiment, before the above-mentioned step S4 for carrying out Authority Verification to the user information, then include：
S4b is verified whether according to the IP address information at the third-party application end within the scope of authority；
In the present embodiment, it is previously stored with the scope of authority list of IP address in the database of server, that is, is limited to
The call request sent in IP address in scope of authority list could be passed through, and the then verifying except the scope of authority does not pass through.
When the IP address information at third-party application end is in the scope of authority, then the described second interim token and described the are verified
Whether one interim token is identical, if in this step, above-mentioned first interim token and the second interim token be not corresponding, then can sentence
The possibility of data is stolen in third-party application end storage of breaking, and in order to ensure secure user data, is then determined as that verifying does not pass through.
In the present embodiment, if above-mentioned second interim token authentication passes through, continue to verify whether the user has access right
Limit, specifically can first judge whether user type meets the requirements, if meeting the requirements, then judge whether user account information conforms to
It asks.Further, the access authority whether user has the application can be not only verified, can also further judge its specific visit
Whether the module asked has corresponding permission.For example, the data application end in the present embodiment has multiple modules, different modules
It is open to different user groups, therefore not only need to verify the permission whether user has access data application end, it is also necessary to
Verify whether it has the permission for accessing some module.
It in another embodiment, further include the time letter of third-party application end sending call request in above-mentioned request of data
Breath.The period that data can be accessed, i.e., within a preset time period, the access of ability turn-on data are preset in server.
In the above-mentioned step S4 for carrying out Authority Verification to the request of data, then also need to verify the sending of third-party application end
Within a preset time period whether time when call request.
In another embodiment, in order to enhance the stability of system, the operating pressure of server is reduced, is called according to history
The user volume of api interface is analyzed, and analyzes which as access peak period period, a limit is arranged according to the peak period period
The list of access time processed is called access in the specified user of peak period period limitation, or directly limitation is useful
Family is not capable of calling.
In one embodiment, it can be combined with the IP address information that user issues call request by third-party application end,
One list is set, the user of IP address accessible in the corresponding period is defined in list.Such as peak period, then it limits
Can only some user is called access inside the province, outside peak period then with no restrictions.
In one embodiment, in peak period, then api interface calling can not be carried out by limiting some third-party application end.Or
Person constantly monitors current amount of access, if amount of access is higher than threshold value, limits designated user and calls access, can be and limit certain
The calling access authority of region user is also possible to limit the power of the calling api interface at some third-party application end of current time
Limit.
If above-mentioned be verified, the API is connect by the third-party application end in one embodiment referring to Fig. 2
After the step S51 of the call request of mouth, including：
The requested page of data of the request of data is shown on the third-party application end by S6.
If being verified, then it represents that user can directly access data application end on third-party application end, and server is then
Corresponding page of data is matched according to user data requests, and page of data is issued on the third-party application end.
Specifically, the above-mentioned step being shown in the request of data requested page of data on the third-party application end
Rapid S6, including：
The content of pages in the page of data is extracted, and obtains the page layout at the third-party application end；Such as
Text picture in page of data is all extracted.
The content of pages of extraction is distributed according to the page layout at the third-party application end, and will be after distribution
Content of pages be shown on the third-party application end.
Since third-party application end is different from the possible frame in data application end, data are directly accessed on third-party application end
When application end, in fact it could happen that the incompatible situation of the page.Therefore, in the present embodiment, by JSOUP component (a kind of Java's
Html parser can directly parse some address URL, html text content) content of pages in page of data is subjected to standard
Change, and the content after standardization is inserted into the according to the page layout at third-party application end by the realization of FILE WITER component
In the page of tripartite's application end.
In conclusion receiving third-party application for the verification method of the calling api interface provided in the embodiment of the present application
When holding to the call request of api interface, the characteristic information for issuing one and the third-party application end establishes the of binding relationship
One interim token is to the third-party application end, the unique identification of the first interim token as third-party application end, avoid by
User data is caused unsafe risk occur when stealing；The operation of input password is carried out without user, while being needed to data
Much information in request is verified, and the data safety of user's access is enhanced, and is simplified user's operation, is overcome current calling
Api interface is cumbersome and calls unsafe defect.
Referring to Fig. 3, present invention also provides a kind of verifying devices for calling api interface, including：
First receiving unit 10, for receiving call request of the third-party application end to api interface, in the call request
Carry the characteristic information at third-party application end.The characteristic information includes the preset third-party application end for having and calling permission
ID and password.Be preset on server in the present embodiment with call permission third-party application end ID list and its
Corresponding password.
In the present embodiment, each third-party application end all has the characteristic information of own, such as ID, password, close
Key etc. is used to indicate the uniqueness at each third-party application end.User (requesting party of data access) is stepped on by account, password
Record above-mentioned third-party application end, and want to open its data application end wanted access on third-party application end, with access its
Data on the data application end, while being not desired to log in above-mentioned data application end again, then need to call the API at the data application end
Interface.In general, the access information (such as icon etc.) at above-mentioned data application end can be set on the third-party application end, use
Family click access information then automatic trigger third-party application end call data application end api interface call request, the calling
It further include the ID for having third-party application end in request.Above-mentioned server is the management server at above-mentioned data application end, server
On the first receiving unit 10 can receive call request of the above-mentioned third-party application end to api interface.Above-mentioned data application end
For any application end, ground of illustrating, for the data application end group in the present embodiment in Django frame, Django is an open-source generation
The Web application framework of code, is write as by Python.The data application end introduces oauth2 standard, can permit use in the standard
Family allows the disconnected resource (such as photo, video, contacts list) for accessing the user on data application end of third-party application, and nothing
Username and password need to be supplied to data application end, purpose is exactly not need input user password login he can be accessed
Resource under system permission, facilitates user to access, and promotes user experience and access efficiency.
Issuance unit 20, for issuing a first interim token to the third-party application according to the call request
End, wherein the first interim token is the interim token that binding relationship is established with the characteristic information at the third-party application end；
In the present embodiment, after server receives above-mentioned third-party application end to the call request of api interface, therefrom obtain
To the ID and password at third-party application end, verify its for it is preset have call permission third-party application end when, issuance unit
20 generate a first interim token (token) according to the ID, and the first interim token and the ID at third-party application end are established
The validity of binding relationship, above-mentioned first interim token has time limit regular hour, such as one minute, half an hour.Other
It, can also be from features described above information in order to further strengthen the safety that api interface is called at third-party application end in embodiment
Key information (there is uniqueness) is got, according to the key at third-party application end and the corresponding generation of ID one there is binding to close
First interim token of system.Above-mentioned interim token can be stolen to avoid other third-party application ends, by modify its ID come into
Row personation is to steal data.
Second receiving unit 30, the request of data sent for receiving user by the third-party application end, the number
According to the user information for carrying the second interim token and the login third-party application end subscriber in request.
It, then will be above-mentioned when third-party application termination receives the first interim token that above-mentioned server issues in the present embodiment
Unique identification of the first interim token as parameter value as third-party application end, while user passes through the third-party application end
Request of data is sent, the second receiving unit 30 then receives above-mentioned request of data.It include that user wants access in the request of data
Data information (user need the operation carried out or the data gone for), the user information of user, interim token, third
The characteristic information etc. of square application end.
When user logs on to third-party application end, which will record user information (user name etc.), when with
User information can be sent to server by the third-party application end when api interface is called by third-party application end in family.According to
Family information can be which third-party application end to call api interface by with identity user, according to the ID at third-party application end with
And user type may determine that whether the user is user in permission.According to the above-mentioned second interim token and the first interim token
It is whether identical, it can be determined that the third-party application end whether be above-mentioned calling api interface application end, avoid being counterfeited.
Authentication unit 40, for when the described first interim token is identical as the described second interim token, to the user
Information carries out Authority Verification；
Due to carrying the data information of access in need in above-mentioned request of data, authentication unit 40 believes above-mentioned user
After the Authority Verification of breath, user then can directly be accessed, without issuing data information again.Here the permission of authentication unit 40
Verifying is exactly to input user password again in order to be implemented without user user directly can be accessed in data application end
Content in extent of competence is realized and exempts from close login.
In the present embodiment, after the second receiving unit 30 gets above-mentioned request of data, in order to reinforce safety, verifying is single
Member 40 needs to carry out Authority Verification to each single item in above-mentioned request of data.For example, can first verify above-mentioned third-party application end is
The no application end that api interface request is called for initiation, then above-mentioned user type and data are checked inside preset permission system
Whether application end matches, and checks whether the user has corresponding operation permission.Judge whether data application end allows to request
The third-party application end of Fang Denglu judges whether the user there are access data to answer according to user name to call data application end
With the permission at end.It in the present embodiment, is verified for each single item information in request of data, multiple-authentication, enhances safety,
User data is avoided to be stolen.
Processing unit 50, for handling the third-party application end and being asked to the calling of the api interface according to verification result
It asks.In the present embodiment, after server is to the Authority Verification of above-mentioned user information, processing can be respectively corresponded according to verification result.
In above process, user is not needed always and carries out corresponding register, and server can be to the access right of user
Limit is verified automatically, simplifies the operation of user；And authentication mechanism when above-mentioned calling api interface has ensured the peace of user data
Quan Xing.
In one embodiment, referring to Fig. 4, above-mentioned processing unit 50 includes：
First processing module 501, if for being verified, by the third-party application end to the api interface
Call request.
Second processing module 502, if not passing through for verifying, feedback includes the verification result of abnormal cause to described
Third-party application end.
In the present embodiment, if the Authority Verification of above-mentioned request of data all passes through, first processing module 501 passes through upper
It states call request and returns to processing result, i.e., permission user accesses its function of wanting access to, and obtains corresponding data.On if
State request of data any one of Authority Verification failure, then verify and do not pass through, Second processing module 502 return verification result, test
Include in card result verifying can not by specific abnormal cause, such as user do not have corresponding authority, third-party application end
Lack of competence etc..
In one embodiment, referring to Fig. 5, above-mentioned authentication unit 40 includes：
Whether the first authentication module 401 is identical for verifying the described first interim token and the described second interim token；
As described in above-mentioned issuance unit 20, the binding relationship for having the first interim token and third-party application end is established, the
One authentication module 401 is then the verifying to third-party application end, if above-mentioned first interim token and the second interim token be not corresponding,
It then may determine that the third-party application end is then judged to verifying in the presence of the possibility for stealing data in order to ensure secure user data
Do not pass through.
Second authentication module 402, if being corresponding for above-mentioned interim token and the characteristic information at the third-party application end
Binding relationship, successively above-mentioned user type and user account information are verified, to verify whether the user has
Access authority.
In the present embodiment, if above-mentioned first authentication module 401 is verified, the second authentication module 402 continues verifying should
Whether user has access authority, specifically can first judge whether user type meets the requirements, if meeting the requirements, then judge user
Whether account information meets the requirements.Further, the access authority whether user has the application can be not only verified, it can be with
Further judge whether the module that it is specifically accessed has corresponding permission.For example, the data application end in the present embodiment has
Multiple modules, different modules is open to different user groups, therefore not only needs to verify whether user has access data
The permission of application end, it is also necessary to verify whether it has the permission for accessing some module.
It in one embodiment, further include the IP address information at the third-party application end in above-mentioned request of data.Third is answered
With end when sending request of data, then IP address information can be uploaded together, it can also be to IP address information in the present embodiment
Permission is verified.
Referring to Fig. 6, in the present embodiment, above-mentioned authentication unit 40 includes：
First verifying subelement 403 verifies whether authorizing for the IP address information according to the third-party application end
In range.
In the present embodiment, it is previously stored with the scope of authority list of IP address in the database of server, that is, is limited to
The call request sent in IP address in scope of authority list could be passed through, and the then verifying except the scope of authority does not pass through.
Second verifying subelement 404, if verifying the second interim token and described first temporarily in the scope of authority
Whether token is identical.
When the IP address information at third-party application end is in the scope of authority, the second verifying subelement 404 then verifies described the
Whether two interim tokens and the described first interim token are identical, if above-mentioned second interim token and the described first interim token be not right
It answers, then may determine that third-party application end storage steals the possibility of data and is then judged to testing to ensure secure user data
Card does not pass through.
Third verifies subelement 405, for if they are the same, then verifying whether the user has access authority.
In the present embodiment, if above-mentioned second verifying subelement 404 is verified, third verifying subelement 405 continues to test
It demonstrate,proves whether the user has access authority, specifically can first judge whether user type meets the requirements, if meeting the requirements, then judge
Whether user account information meets the requirements.Further, the access authority whether user has the application can be not only verified, also
Whether the module that can further judge that it is specifically accessed has corresponding permission.For example, the data application end in the present embodiment
With multiple modules, different modules is open to different user groups, therefore not only needs to verify whether user has access
The permission at data application end, it is also necessary to verify whether it has the permission for accessing some module.
It in another embodiment, further include the time letter of third-party application end sending call request in above-mentioned request of data
Breath.The period that data can be accessed, i.e., within a preset time period, the access of ability turn-on data are preset in server.
Above-mentioned authentication unit 40 then also needs to verify whether time when third-party application end issues call request is presetting
Period in.
In another embodiment, in order to enhance the stability of system, the operating pressure of server is reduced, is called according to history
The user volume of api interface is analyzed, and analyzes which as access peak period period, a limit is arranged according to the peak period period
The list of access time processed is called access in the specified user of peak period period limitation, or directly limitation is useful
Family is not capable of calling.
In one embodiment, it can be combined with the IP address information that user issues call request by third-party application end,
One list is set, the user of IP address accessible in the corresponding period is defined in list.Such as peak period, then it limits
Can only some user is called access inside the province, outside peak period then with no restrictions.
In one embodiment, in peak period, then api interface calling can not be carried out by limiting some third-party application end.Or
Person constantly monitors current amount of access, if amount of access is higher than threshold value, limits designated user and calls access, can be and limit certain
The calling access authority of region user is also possible to limit the power of the calling api interface at some third-party application end of current time
Limit.
In one embodiment, the verifying device of above-mentioned calling api interface further includes：
Display unit, for the requested page of data of the request of data to be shown in the third-party application end.
If being verified, then it represents that user can directly access data application end, display unit on third-party application end
Corresponding page of data then is matched according to user data requests, and page of data is issued on the third-party application end.
Specifically, above-mentioned display unit includes：
Extraction module for extracting the content of pages in the page of data, and obtains the third-party application end
Page layout；Such as the text picture in page of data is all extracted.
Display module, for being divided the content of pages extracted according to the page layout at the third-party application end
Cloth, and the content of pages after distribution is shown on the third-party application end.
Since third-party application end is different from the possible frame in data application end, data are directly accessed on third-party application end
When application end, in fact it could happen that the incompatible situation of the page.Therefore, in the present embodiment, by JSOUP component (a kind of Java's
Html parser can directly parse some address URL, html text content) content of pages in page of data is subjected to standard
Change, and the content after standardization is inserted into the according to the page layout at third-party application end by the realization of FILE WITER component
In the page of tripartite's application end.
In conclusion receiving third-party application for the verifying device of the calling api interface provided in the embodiment of the present application
When holding the call request to api interface, the characteristic information at third-party application end, the feature letter are carried in the call request
Breath is the ID and password at the preset third-party application end for having and calling permission；Issue the spy of one with the third-party application end
Reference breath establishes the first interim token of binding relationship to the third-party application end, which answers as third party
With the unique identification at end, user data is caused unsafe risk occur when avoiding being stolen；Input password is carried out without user
Operation, while needing to verify the much information in request of data, enhance the data safety of user's access, simplify and use
Family operation overcomes and calls api interface cumbersome at present and the unsafe defect of calling.
Referring to Fig. 7, a kind of computer equipment is also provided in the embodiment of the present application, which can be server,
Its internal structure can be as shown in Figure 7.The computer equipment includes processor, the memory, network connected by system bus
Interface and database.Wherein, the processor of the Computer Design is for providing calculating and control ability.The computer equipment is deposited
Reservoir includes non-volatile memory medium, built-in storage.The non-volatile memory medium is stored with operating system, computer program
And database.The built-in storage provides environment for the operation of operating system and computer program in non-volatile memory medium.
The database of the computer equipment is for storing the data such as computer program.The network interface of the computer equipment is used for and outside
Terminal by network connection communication.To realize a kind of verifying for calling api interface when the computer program is executed by processor
Method.
Above-mentioned processor executes the step of verification method of above-mentioned calling api interface and includes：Server receives third party and answers
With call request of the end to api interface, the characteristic information at third-party application end, the feature letter are carried in the call request
Breath is the ID and password at the preset third-party application end for having and calling permission；
According to the call request, a first interim token is issued to the third-party application end, wherein described first
Interim token is the interim token that binding relationship is established with the characteristic information at the third-party application end；
The request of data that user is sent by the third-party application end is received, it is interim to carry second in the request of data
Token and the user information for logging in the third-party application end subscriber；
When the described first interim token is identical as the described second interim token, permission is carried out to the user information and is tested
Card；
According to verification result, call request of the third-party application end to the api interface is handled.
In one embodiment, above-mentioned processor handles the third-party application end to the api interface according to verification result
Call request the step of, including：
Call request if being verified, by the third-party application end to the api interface；If verifying obstructed
It crosses, then feedback includes the verification result of abnormal cause to the third-party application end.
In one embodiment, above-mentioned user information includes user type and user account information, and above-mentioned processor is to institute
Stating the step of user information carries out Authority Verification includes：
Successively the user type and user account information are verified, to verify whether the user has access
Permission.
It in one embodiment, further include the IP address information at the third-party application end in above-mentioned request of data.
In one embodiment, before the step of above-mentioned processor carries out Authority Verification to the user information, including：
According to the IP address information at the third-party application end, verify whether within the scope of authority.
In one embodiment, above-mentioned processor is verified, then by the third-party application end to the api interface
After the step of call request, including：
The requested page of data of the request of data is shown on the third-party application end.
In one embodiment, the requested page of data of the request of data is shown in the third party by above-mentioned processor
Step in application end, including：
The content of pages in the page of data is extracted, and obtains the page layout at the third-party application end；
The content of pages of extraction is distributed according to the page layout at the third-party application end, and will be after distribution
Content of pages be shown on the third-party application end.
It will be understood by those skilled in the art that structure shown in Fig. 7, only part relevant to application scheme is tied
The block diagram of structure does not constitute the restriction for the computer equipment being applied thereon to application scheme.
One embodiment of the application also provides a kind of computer storage medium, is stored thereon with computer program, computer journey
A kind of verification method for calling api interface is realized when sequence is executed by processor, specially：Server receives third-party application end pair
The call request of api interface carries the characteristic information at third-party application end in the call request, and the characteristic information is pre-
If have call permission third-party application end ID and password；
According to the call request, a first interim token is issued to the third-party application end, wherein described first
Interim token is the interim token that binding relationship is established with the characteristic information at the third-party application end；
The request of data that user is sent by the third-party application end is received, it is interim to carry second in the request of data
Token and the user information for logging in the third-party application end subscriber；
When the described first interim token is identical as the described second interim token, permission is carried out to the user information and is tested
Card；
According to verification result, call request of the third-party application end to the api interface is handled.
In one embodiment, above-mentioned processor handles the third-party application end to the api interface according to verification result
Call request the step of, including：
Call request if being verified, by the third-party application end to the api interface；If verifying obstructed
It crosses, then feedback includes the verification result of abnormal cause to the third-party application end.
In one embodiment, above-mentioned user information includes user type and user account information, and above-mentioned processor is to institute
Stating the step of user information carries out Authority Verification includes：
Successively the user type and user account information are verified, to verify whether the user has access
Permission.
It in one embodiment, further include the IP address information at the third-party application end in above-mentioned request of data.
In one embodiment, before the step of above-mentioned processor carries out Authority Verification to the user information, including：
According to the IP address information at the third-party application end, verify whether within the scope of authority.
In one embodiment, above-mentioned processor is verified, then by the third-party application end to the api interface
After the step of call request, including：
The requested page of data of the request of data is shown on the third-party application end.
In one embodiment, the page of data of request described in the request of data is shown in the third by above-mentioned processor
Step in square application end, including：
The content of pages in the page of data is extracted, and obtains the page layout at the third-party application end；
The content of pages of extraction is distributed according to the page layout at the third-party application end, and will be after distribution
Content of pages be shown on the third-party application end.
In conclusion for verification method, the device, computer equipment of the calling api interface provided in the embodiment of the present application
And storage medium, when receiving call request of the third-party application end to api interface, issue one and the third-party application end
Characteristic information establish the first interim token of binding relationship to the third-party application end, the first interim token is as third
The unique identification of square application end causes user data unsafe risk occur when avoiding being stolen；It is inputted without user
The operation of password, while needing to verify the much information in request of data, enhance the data safety of user's access, letter
Change user's operation, overcomes and call api interface cumbersome at present and the unsafe defect of calling.
Those of ordinary skill in the art will appreciate that realizing all or part of the process in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the computer program can store and a non-volatile computer
In read/write memory medium, the computer program is when being executed, it may include such as the process of the embodiment of above-mentioned each method.Wherein,
Any reference used in provided herein and embodiment to memory, storage, database or other media,
Including non-volatile and/or volatile memory.Nonvolatile memory may include read-only memory (ROM), programming ROM
(PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM) or flash memory.Volatile memory may include
Random access memory (RAM) or external cache.By way of illustration and not limitation, RAM can by diversified forms
, such as static state RAM (SRAM), dynamic ram (DRAM), synchronous dram (SDRAM), double speed are according to rate SDRAM (SSRSDRAM), increasing
Strong type SDRAM (ESDRAM), synchronization link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM
(RDRAM), direct memory bus dynamic ram (DRDRAM) and memory bus dynamic ram (RDRAM) etc..
It should be noted that, in this document, the terms "include", "comprise" or its any other variant are intended to non-row
His property includes, so that the process, device, article or the method that include a series of elements not only include those elements, and
And further include the other elements being not explicitly listed, or further include for this process, device, article or method institute it is intrinsic
Element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that including being somebody's turn to do
There is also other identical elements in the process, device of element, article or method.
The foregoing is merely preferred embodiment of the present application, are not intended to limit the scope of the patents of the application, all utilizations
Equivalent structure or equivalent flow shift made by present specification and accompanying drawing content is applied directly or indirectly in other correlations
Technical field, similarly include in the scope of patent protection of the application.
Claims (10)
1. a kind of verification method for calling api interface, which is characterized in that include the following steps：
Call request of the third-party application end to api interface is received, the spy at third-party application end is carried in the call request
Reference breath, the characteristic information are the ID and password at the preset third-party application end for having and calling permission；
According to the call request, a first interim token is issued to the third-party application end, wherein described first is interim
Token is the interim token that binding relationship is established with the characteristic information at the third-party application end；
The request of data that user is sent by the third-party application end is received, carries the second interim token in the request of data
And log in the user information of the third-party application end subscriber；
When the described first interim token is identical as the described second interim token, Authority Verification is carried out to the user information；
According to verification result, call request of the third-party application end to the api interface is handled.
2. the verification method according to claim 1 for calling api interface, which is characterized in that described according to verification result, place
The step of managing call request of the third-party application end to the api interface, including：
Call request if being verified, by the third-party application end to the api interface；If verifying does not pass through,
Feedback includes the verification result of abnormal cause to the third-party application end.
3. the verification method according to claim 1 for calling api interface, which is characterized in that the user information includes using
Family type and user account information, described the step of Authority Verification is carried out to the user information, including：
Successively the user type and user account information are verified, to verify whether the user has access right
Limit.
4. the verification method according to claim 1 for calling api interface, which is characterized in that also wrapped in the request of data
Include the IP address information at the third-party application end.
5. the verification method according to claim 4 for calling api interface, which is characterized in that described to the user information
Before the step of carrying out Authority Verification, including：
According to the IP address information at the third-party application end, verify whether within the scope of authority.
6. the verification method according to claim 2 for calling api interface, which is characterized in that if described be verified, lead to
After the step of crossing call request of the third-party application end to the api interface, including：
The requested page of data of the request of data is shown on the third-party application end.
7. the verification method according to claim 6 for calling api interface, which is characterized in that described by the request of data
Requested page of data is shown in the step on the third-party application end, including：
The content of pages in the page of data is extracted, and obtains the page layout at the third-party application end；
The content of pages of extraction is distributed according to the page layout at the third-party application end, and by the page after distribution
Face content is shown on the third-party application end.
8. a kind of verifying device for calling api interface, which is characterized in that including：
First receiving unit carries in the call request for receiving call request of the third-party application end to api interface
The characteristic information at third-party application end, the characteristic information are preset to have the ID at third-party application end for calling permission and close
Code；
Issuance unit, for according to the call request, issuing a first interim token to the third-party application end,
In, the first interim token is the first interim token that binding relationship is established with the characteristic information at the third-party application end；
Second receiving unit, the request of data sent for receiving user by the third-party application end, the request of data
The middle user information for carrying the second interim token and logging in the third-party application end subscriber；
Authentication unit, for when the described first interim token is identical as the described second interim token, to the user information into
Row Authority Verification；
Processing unit, for handling call request of the third-party application end to the api interface according to verification result.
9. a kind of computer equipment, including memory and processor, the memory are stored with computer program, feature exists
In the step of processor realizes any one of claims 1 to 7 the method when executing the computer program.
10. a kind of computer storage medium, is stored thereon with computer program, which is characterized in that the computer program is located
The step of reason device realizes method described in any one of claims 1 to 7 when executing.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810421551.3A CN108830099A (en) | 2018-05-04 | 2018-05-04 | Call verification method, device, computer equipment and the storage medium of api interface |
| PCT/CN2018/095672 WO2019210579A1 (en) | 2018-05-04 | 2018-07-13 | Verification method and apparatus for invoking api interface, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810421551.3A CN108830099A (en) | 2018-05-04 | 2018-05-04 | Call verification method, device, computer equipment and the storage medium of api interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108830099A true CN108830099A (en) | 2018-11-16 |
Family
ID=64147484
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810421551.3A Pending CN108830099A (en) | 2018-05-04 | 2018-05-04 | Call verification method, device, computer equipment and the storage medium of api interface |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108830099A (en) |
| WO (1) | WO2019210579A1 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109614778A (en) * | 2018-12-12 | 2019-04-12 | 苏州思必驰信息科技有限公司 | Dynamic Configuration, gateway and the system of user right |
| CN109871287A (en) * | 2018-12-15 | 2019-06-11 | 中国平安人寿保险股份有限公司 | Interface call method, device, computer installation and storage medium |
| CN110007950A (en) * | 2019-04-10 | 2019-07-12 | 优信拍（北京）信息科技有限公司 | A kind of management method of application programming interfaces, device and server |
| CN110414215A (en) * | 2019-06-21 | 2019-11-05 | 北京奇艺世纪科技有限公司 | Application program privacy authority states bearing calibration, device and electronic equipment |
| CN110740163A (en) * | 2019-09-04 | 2020-01-31 | 无锡华云数据技术服务有限公司 | Idempotent control method, idempotent control device, electronic equipment and readable storage medium |
| CN111901342A (en) * | 2020-07-28 | 2020-11-06 | 平安科技（深圳）有限公司 | Authority application verification method, device, equipment and storage medium |
| WO2020233012A1 (en) * | 2019-05-20 | 2020-11-26 | 平安科技（深圳）有限公司 | Distributed smart api asynchronous callback method, device, client terminal, service terminal, and storage medium |
| CN112738167A (en) * | 2020-12-18 | 2021-04-30 | 福建新大陆软件工程有限公司 | File service opening method, device, equipment and medium based on API gateway |
| CN114244563A (en) * | 2021-11-15 | 2022-03-25 | 珠海许继芝电网自动化有限公司 | Front-end and back-end cross-language communication method and system based on AES encryption |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111601038B (en) * | 2020-05-28 | 2021-10-01 | 无锡睿勤科技有限公司 | Camera control method and device, electronic terminal and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102378170A (en) * | 2010-08-27 | 2012-03-14 | 中国移动通信有限公司 | Method, device and system of authentication and service calling |
| CN103051630A (en) * | 2012-12-21 | 2013-04-17 | 微梦创科网络科技（中国）有限公司 | Method, device and system for implementing authorization of third-party application based on open platform |
| CN104519018A (en) * | 2013-09-29 | 2015-04-15 | 阿里巴巴集团控股有限公司 | Method, device and system for preventing malicious requests for server |
| US20150215305A1 (en) * | 2013-12-11 | 2015-07-30 | Capital One Financial Corporation | Systems and methods for populating online applications using third party platforms |
| CN106302346A (en) * | 2015-05-27 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The safety certifying method of API Calls, device, system |
| CN106506494A (en) * | 2016-10-27 | 2017-03-15 | 上海斐讯数据通信技术有限公司 | Application access method of open platform |
| CN106897586A (en) * | 2016-08-04 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of application programming interface API right management methods and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5892900A (en) * | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
| CN103609090B (en) * | 2013-06-19 | 2017-06-06 | 华为技术有限公司 | Identity logs method and apparatus |
| CN103716326B (en) * | 2013-12-31 | 2017-02-01 | 华为技术有限公司 | Resource access method and URG |
| CN106961332B (en) * | 2016-01-11 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Authority authentication method and device |
-
2018
- 2018-05-04 CN CN201810421551.3A patent/CN108830099A/en active Pending
- 2018-07-13 WO PCT/CN2018/095672 patent/WO2019210579A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102378170A (en) * | 2010-08-27 | 2012-03-14 | 中国移动通信有限公司 | Method, device and system of authentication and service calling |
| CN103051630A (en) * | 2012-12-21 | 2013-04-17 | 微梦创科网络科技（中国）有限公司 | Method, device and system for implementing authorization of third-party application based on open platform |
| CN104519018A (en) * | 2013-09-29 | 2015-04-15 | 阿里巴巴集团控股有限公司 | Method, device and system for preventing malicious requests for server |
| US20150215305A1 (en) * | 2013-12-11 | 2015-07-30 | Capital One Financial Corporation | Systems and methods for populating online applications using third party platforms |
| CN106302346A (en) * | 2015-05-27 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The safety certifying method of API Calls, device, system |
| CN106897586A (en) * | 2016-08-04 | 2017-06-27 | 阿里巴巴集团控股有限公司 | A kind of application programming interface API right management methods and device |
| CN106506494A (en) * | 2016-10-27 | 2017-03-15 | 上海斐讯数据通信技术有限公司 | Application access method of open platform |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109614778A (en) * | 2018-12-12 | 2019-04-12 | 苏州思必驰信息科技有限公司 | Dynamic Configuration, gateway and the system of user right |
| CN109871287A (en) * | 2018-12-15 | 2019-06-11 | 中国平安人寿保险股份有限公司 | Interface call method, device, computer installation and storage medium |
| CN110007950A (en) * | 2019-04-10 | 2019-07-12 | 优信拍（北京）信息科技有限公司 | A kind of management method of application programming interfaces, device and server |
| WO2020233012A1 (en) * | 2019-05-20 | 2020-11-26 | 平安科技（深圳）有限公司 | Distributed smart api asynchronous callback method, device, client terminal, service terminal, and storage medium |
| CN110414215A (en) * | 2019-06-21 | 2019-11-05 | 北京奇艺世纪科技有限公司 | Application program privacy authority states bearing calibration, device and electronic equipment |
| CN110740163A (en) * | 2019-09-04 | 2020-01-31 | 无锡华云数据技术服务有限公司 | Idempotent control method, idempotent control device, electronic equipment and readable storage medium |
| CN110740163B (en) * | 2019-09-04 | 2021-04-02 | 华云数据控股集团有限公司 | Idempotent control method, idempotent control device, electronic equipment and readable storage medium |
| CN111901342A (en) * | 2020-07-28 | 2020-11-06 | 平安科技（深圳）有限公司 | Authority application verification method, device, equipment and storage medium |
| WO2021139244A1 (en) * | 2020-07-28 | 2021-07-15 | 平安科技（深圳）有限公司 | Permissions request verification method and apparatus, device, and storage medium |
| CN111901342B (en) * | 2020-07-28 | 2022-06-17 | 平安科技（深圳）有限公司 | Authority application verification method, device, equipment and storage medium |
| CN112738167A (en) * | 2020-12-18 | 2021-04-30 | 福建新大陆软件工程有限公司 | File service opening method, device, equipment and medium based on API gateway |
| CN114244563A (en) * | 2021-11-15 | 2022-03-25 | 珠海许继芝电网自动化有限公司 | Front-end and back-end cross-language communication method and system based on AES encryption |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019210579A1 (en) | 2019-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108830099A (en) | Call verification method, device, computer equipment and the storage medium of api interface | |
| CN103249045B (en) | A kind of methods, devices and systems of identification | |
| CA2930335C (en) | System and method for credentialed access to a remote server | |
| CN108200050A (en) | Single logging-on server, method and computer readable storage medium | |
| CN106487774A (en) | A kind of cloud host services authority control method, device and system | |
| CN105871838A (en) | Third party account login control method and user center platform | |
| CN107992771B (en) | A kind of data desensitization method and device | |
| CN110149328A (en) | Interface method for authenticating, device, equipment and computer readable storage medium | |
| CN109873805A (en) | Cloud desktop login method, device, equipment and storage medium based on cloud security | |
| CN106341234A (en) | Authorization method and device | |
| CN109547458A (en) | Login validation method, device, computer equipment and storage medium | |
| CN111818088A (en) | Authorization mode management method and device, computer equipment and readable storage medium | |
| CN110113366A (en) | A kind of detection method and device of CSRF loophole | |
| CN107277015A (en) | Unifying user authentication management method, system, storage medium and server | |
| CN108600234A (en) | A kind of auth method, device and mobile terminal | |
| CN112434054A (en) | Audit log updating method and device | |
| CN107645474B (en) | Method and device for logging in open platform | |
| CN115982694A (en) | Resource access method, device, equipment and medium | |
| CN107580002A (en) | Double factor authentication safety management machine login system and method | |
| CN112929388B (en) | Network identity cross-device application rapid authentication method and system, and user agent device | |
| CN110166471A (en) | A kind of portal authentication method and device | |
| CN110324307A (en) | A kind of single sign-on authentication method and relevant device based on cloud | |
| CN105656856A (en) | Resource management method and device | |
| CN103281296B (en) | The method and apparatus for handling encrypted message | |
| CN110162941A (en) | A kind of terminal log-on message store method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181116 |