CN117762601A - Method, system, terminal and storage medium for invoking hydra service - Google Patents
Method, system, terminal and storage medium for invoking hydra service Download PDFInfo
- Publication number
- CN117762601A CN117762601A CN202410194846.7A CN202410194846A CN117762601A CN 117762601 A CN117762601 A CN 117762601A CN 202410194846 A CN202410194846 A CN 202410194846A CN 117762601 A CN117762601 A CN 117762601A
- Authority
- CN
- China
- Prior art keywords
- service
- hydra
- package
- configuration
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 241000243251 Hydra Species 0.000 title claims abstract description 95
- QRXWMOHMRWLFEY-UHFFFAOYSA-N isoniazide Chemical compound NNC(=O)C1=CC=NC=C1 QRXWMOHMRWLFEY-UHFFFAOYSA-N 0.000 title claims abstract description 95
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000005538 encapsulation Methods 0.000 claims abstract description 41
- 238000004806 packaging method and process Methods 0.000 claims abstract description 30
- 238000012545 processing Methods 0.000 claims abstract description 18
- ZZUFCTLCJUWOSV-UHFFFAOYSA-N furosemide Chemical compound C1=C(Cl)C(S(=O)(=O)N)=CC(C(O)=O)=C1NCC1=CC=CO1 ZZUFCTLCJUWOSV-UHFFFAOYSA-N 0.000 claims description 23
- 239000007858 starting material Substances 0.000 claims description 18
- 238000013475 authorization Methods 0.000 claims description 15
- 230000006870 function Effects 0.000 claims description 12
- 238000010276 construction Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000014509 gene expression Effects 0.000 description 2
- 238000012858 packaging process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007429 general method Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The invention relates to the field of hydra service, and particularly discloses a hydra service calling method, a system, a terminal and a storage medium, wherein configuration classes and service interfaces of hydra service are packaged, a packaging package is constructed, and the packaging package exposes configuration files and the packaged service interfaces to an application program; the application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package; the encapsulation package reads the configured parameters mapped to the native service of the hydra; the application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement. According to the invention, the bridge is established between the hydra service and the application program by constructing the package containing the hydra configuration class and the interface, so that the application program can use the hydra service by calling the package, the convenience of calling the hydra service is improved, and the working efficiency is improved.
Description
Technical Field
the invention relates to the field of hydra service, in particular to a hydra service calling method, a system, a terminal and a storage medium.
Background
Ory hydro is an enhanced, openID authenticated OAuth 2.0 server and OpenID Connect provider, optimized for low latency, high throughput and low resource consumption. The ORY Hydroa is not an identity provider (user registration, user login, password reset procedure), but is connected to an existing identity provider through a login and consent application.
Currently, hydra is mainly used to deal with single sign-on and authorization issues between systems. However, the native interface provided by the hydra cannot adapt to the requirements of the application program, when the application program calls the hydra, a great amount of logic codes are written, a great amount of parameters are configured and a great number of classes needed by the hydra are injected into the application program, and the current repackaging scheme for the hydra interface is scarce, so that the application developer can be helped to develop a frame based on the hydra quickly, the call of the application program to the hydra is complicated, and the working efficiency is affected.
Disclosure of Invention
In order to solve the problems, the invention provides a method, a system, a terminal and a storage medium for invoking a hydra service, wherein a bridge is established between the hydra service and an application program by constructing a package containing a hydra configuration class and an interface, so that the application program can use the hydra service by invoking the package, the convenience of invoking the hydra service is improved, and the working efficiency is improved.
In a first aspect, the present invention provides a method for invoking a hydro service, including the following steps:
Packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
The application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package;
The encapsulation package reads the configured parameters mapped to the native service of the hydra;
The application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
In an alternative embodiment, the configuration class of the hydra service is encapsulated, which specifically includes:
integrating configuration classes originally required by the hydra service into codes;
The customized parameters in the configuration class are exposed to the application in the form of a configuration file.
In an alternative embodiment, the encapsulated service interface includes a core business package, an entity class, and a token handle.
In an alternative embodiment, the core service package includes a first service package and a second service package, the first service package provides a method for implementing redirection, exiting redirection, logging out and obtaining a token by a callback, and the second service package provides subsequent processing logic and returned content of operation failure and success.
in an alternative embodiment, when the service interface of the hydro a service is encapsulated, the relevant interceptor extended authentication function is also written for encapsulation.
In an alternative embodiment, the encapsulated interceptors include a first interceptor, a second interceptor, a third interceptor, and a fourth interceptor;
The first interceptor comprises a log recorder and provides a method for judging whether a certain URI needs to be removed, a method for judging whether a request needs to bypass OAuth authentication and a method for setting an unauthorized response state code;
The second interceptor is used for authenticating and authorizing the request of the user and providing execution logic when the authorization fails; wherein authenticating the user request includes attempting to verify whether the user's token has expired, if so, using the refresh token to refresh the token, if so, updating the user information and saving the information in the session, if so, indicating that the user request fails authentication, the request will be denied; meanwhile, storing the authentication result requested by the user into the attribute of the request;
the third interceptor is used for providing a method for judging the validity of the token and the parameters acquired from the header;
The fourth interceptor is used to check if the request has been validated by OAuth and has sufficient rights to access the request handler.
in an alternative embodiment, the encapsulation packet is a starter packet.
in a second aspect, the present invention provides a system for invoking a hydro service, including,
And (3) an encapsulation package construction module: packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
And (5) an encapsulation package calling module: the application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package; the encapsulation package reads the configured parameters mapped to the native service of the hydra; the application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
In a third aspect, a technical solution of the present invention provides a terminal, including:
a memory for storing a hydra service calling program;
And the processor is used for realizing the steps of the hydra service calling method when executing the hydra service calling program.
in a fourth aspect, the present invention provides a computer readable storage medium, where a hydro a service calling program is stored, where the hydro a service calling program when executed by a processor implements the steps of the hydro a service calling method according to any one of the above claims.
Compared with the prior art, the method, the device, the terminal and the storage medium for invoking the hydra service have the following beneficial effects: and packaging the configuration class and the service interface of the hydra service to construct a packaging package, wherein an application program only needs to fill in a small amount of configuration parameters, and can obtain more useful service information and less configuration experience without writing a large amount of codes. According to the invention, the bridge is established between the hydra service and the application program by constructing the package containing the hydra configuration class and the interface, so that the application program can use the hydra service by calling the package, the convenience of calling the hydra service is improved, and the working efficiency is improved.
Drawings
For a clearer description of embodiments of the invention or of the prior art, the drawings that are used in the description of the embodiments or of the prior art will be briefly described, it being apparent that the drawings in the description below are only some embodiments of the invention, and that other drawings can be obtained from them without inventive effort for a person skilled in the art.
fig. 1 is a schematic flow chart of a method for calling a service by using a hydro service according to an embodiment of the present invention.
Fig. 2 is a schematic block diagram of a hydro service call service system according to an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to better understand the aspects of the present invention, the present invention will be described in further detail with reference to the accompanying drawings and detailed description. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
some of the key terms appearing in the present invention are explained below.
OAuth: the OAuth protocol provides a secure, open, and easy standard for authorization of user resources. The difference from the previous authorization mode is that the OAUTH authorization does not enable the third party to touch the account information (such as the user name and the password) of the user, i.e. the third party can apply for obtaining the authorization of the user resource without using the user name and the password of the user, so that the OAUTH is safe. oAuth is a shorthand for Open Authorization.
The interface of the hydra native is process-oriented, complex, high in learning cost and high in code writing difficulty. According to the embodiment, the hydra service is secondarily packaged, so that the hydra service has the object-oriented convenient characteristic, a bridge is built between the hydra native service and the application program, the application program does not need to call a hydra native interface which is not good, and more useful service information and less configuration experience can be obtained only by calling a starter package packaged interface.
Fig. 1 is a schematic flow chart of a method for calling a service by using a hydro service according to an embodiment of the present invention. The execution body of fig. 1 may be a hydro service invocation system. The method for calling the hydra service provided by the embodiment of the invention is executed by the computer equipment, and correspondingly, the hydra service calling system is operated in the computer equipment. The order of the steps in the flow chart may be changed and some may be omitted according to different needs.
As shown in fig. 1, the method includes the following steps.
s1, packaging configuration classes and service interfaces of the hydra service, constructing a packaging package, and exposing the configuration files and the packaged service interfaces to an application program by the packaging package.
S2, the application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package.
s3, the packaging package reads the configured parameters to be mapped into the native service of the hydra.
S4, the application program calls the relevant packaged service interface based on the service requirement to trigger the hydra service to carry out service processing.
The configuration class and the service interface of the hydra service are encapsulated firstly to construct an encapsulation package, and an application program directly calls the encapsulation package to realize the call of the hydra service without writing a large amount of codes to call the hydra service. Wherein the encapsulation packet may be a starter packet.
The embodiment encapsulates the configuration class of the hydra service, and specifically includes the following steps: integrating configuration classes originally required by the hydra service into codes; the customized parameters in the configuration class are exposed to the application in the form of a configuration file. Specifically, the parameters needed by the original hydra service are configured and modified, namely, configuration classes needed by the original hydra are integrated into codes, and the customized parameters needed by the classes are exposed to an application program in a configuration mode. Therefore, the package of this embodiment decouples the hydra service and the application program, directly realizes writing of the configuration class related to hydra in the package, exposes the parameters to be customized to the application program in the configuration form, and the application program can be read by the starter package only by writing the custom parameters into the configuration file and mapped to the service native to hydra.
In addition to encapsulating the configuration class, the service interface needs to be encapsulated to handle the traffic. The encapsulation native hydra service interface of the embodiment performs secondary encapsulation of the object on the basis of the original interface. The service interface encapsulated in this embodiment includes a core service package, an entity class, and a token handle.
Core service package (Cotroller): the related operations of the hydra are encapsulated and exposed to the application program that needs to be used. Mainly comprises a first service packet and a second service packet.
first service package (oauthhydrolcontrol): methods for implementing redirection, exiting redirection, logging out, and obtaining token by callback are provided. These methods encapsulate based on hydra and are exposed externally to the application that invoked the package.
Second service package (OauthResponseController): subsequent processing logic and returned content for failed and successful operations is provided. Also exposed to the outside.
The entity class is used to define object class information used by the interface.
Token handle: clientCredential and UserThreadLocal are entity classes that are needed in the packaging process and are not described in detail. OauthManager is a tool class prepared for an application system, providing a method for acquiring a corresponding client credential (Client Credential) object and for revoking (revoking) a token (token) of a certain client from the application's clientId.
In addition, the util package can be packaged, most of the tools which are used internally in the packaging process and are convenient to develop are not needed to be concerned by specific businesses.
The embodiment performs secondary development on the basis of packaging the hydra service, writes the functions of the related interceptor in terms of extended authentication, and provides more functional interfaces. The interceptors encapsulated in this embodiment include a first interceptor, a second interceptor, a third interceptor, and a fourth interceptor, and each interceptor will be described in detail below.
First interceptor (abstract interjector): some general methods and logic are provided for implementing an interceptor of OAuth. Specific interceptor functions require subclasses to implement, and specific logic is implemented by overlaying the corresponding methods. Mainly comprises: the log recorder provides a method for judging whether a certain URI needs to be eliminated, a method for judging whether a request needs to bypass OAuth authentication or not and a method for setting an unauthorized response state code.
Second interceptor (authenticationInterceptor): authenticating and authorizing the user's request, it will try to check if the user's token has expired, if expired and the user has a refresh token, then refresh the token with the refresh token, if the refresh is successful, then update the user information and save the information in the session, if the refresh is failed, then indicate that the user request is not authenticated, the request will be denied; meanwhile, the result of authentication requested by the user is stored in the attribute of the request, so that the subsequent processing is convenient. At the same time, this class provides a method that is performed when authorization fails.
third interceptor (AuthorizationInterceptor): methods for determining token validity and parameters obtained from a header are provided.
fourth interceptor (interceptor handle): for checking whether the request has been validated by OAuth and has sufficient rights to access the request handler.
Based on the packaged starter package, when a third party application needs single sign-on, only a small amount of key parameter configuration is carried out in yml files after the starter package is introduced, and the object and method packaged by the starter package can be used for acquiring the single sign-on information and controlling the sign-on flow in the places such as application sign-on logic and business processing, so that the application does not need to independently interface with the hydra service.
When using the starter package, the dependencies are imported first, then the configuration is added, and then the traffic processing is performed. Wherein the added configuration comprises a conventional web project single sign-on scene configuration, a front-end and back-end separation-single sign-on scene configuration, an api authorization scene configuration and the like. The business processes include authentication, cancellation, authorization, etc.
(1) Authentication
two modes are distinguished: an organization_code mode and a client_differential mode.
The authorization_code mode: the method is mainly applied to single sign-on of the three-party application integration Oauth2, and supports calling of application interfaces in other Oauth2 authorizations; acquiring a token; the token management is built in, so that the problems of expiration and the like are not required to be concerned; regarding interface call, the starter package is built with two ways for requesting an http interface, oauth2 must use an http client provided by the starter, and the client has been automatically given a token; regarding the callback extension, in the authorization_code mode, the starter packet defaults to realize the callback method, the path is/oauth/callback, and the callback method mainly realizes the creation of the exchange token and the local userInfo.
client_differential mode: the method is mainly applied to calling application interfaces in other Oauth2 authorizations; acquiring a token, managing the built-in token, and not needing to care about the problems of expiration and the like, if a starter is introduced, only using a client credentials mode, disabling the authorization code mode, and enabling the system to be turned off by configuring cnhealth. Regarding interface calls, the starter package embeds two ways for requesting an http interface, the Oauth2 task must use the http client provided by the starter, which has been automatically assigned to the token.
(2) Logging out
single sign-out refers to that the same browser accesses a plurality of applications, after single sign-on occurs, all application sessions of the current browser expire after a certain application executes a sign-out operation.
And (3) exiting configuration: exiting address registration, referring to redirect address registration; upgrading oauth-spring-boot-starter to a version above 1.0.6.1; front end exit logical exit address points to/oauth/logo forward; the token logs off.
The exit operation includes a token logout operation, except that the token OauthManager is independently logout in client mode.
Regarding extradecpatterns, starters include support for two configurations: application, properties configuration, supporting matching expressions using spring; annotation configuration, the @ Oauth2Exclude tag may be used for the controller class or method.
(3) Authorization
Regarding authenticationExcludePathPatterns, starters support two configurations: application, properties configuration, supporting matching expressions using spring; annotation configuration, the @ oauthorizationExclude tag can be used for the controller class or method.
Regarding scope, when the authentication end authenticates the resource, the authority verification can be performed based on scope: the issued client is provided with a scope, and the request end carries a scope initiating request; the authentication terminal can perform token authentication according to the scope defined by the interface or the scope of the global configuration.
the embodiment of the invention provides a method for calling the hydra service, which is characterized in that the method for calling the hydra service is used for calling the hydra service.
Fig. 2 is a schematic block diagram of a architecture of a hydro a service invocation system according to an embodiment of the present invention, where the hydro a service invocation system 200 may be divided into a plurality of functional modules according to the functions performed by the system, as shown in fig. 2. The functional module may include: the package comprises a package construction module 210 and a package calling module 220. The module referred to in the present invention refers to a series of computer program segments capable of being executed by at least one processor and of performing a fixed function, stored in a memory.
the encapsulation package construction module 210: and packaging the configuration class and the service interface of the hydra service to construct a packaging package, wherein the packaging package exposes the configuration file and the packaged service interface to the application program.
The encapsulation package calling module 220: the application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package; the encapsulation package reads the configured parameters mapped to the native service of the hydra; the application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
The hydro a service calling system of this embodiment is used to implement the foregoing hydro a service calling method, so the detailed implementation of this system can be found in the foregoing example section of the hydro a service calling method, so the detailed implementation of this system can refer to the description of the corresponding examples of the various sections, and will not be described herein.
In addition, since the hydro a service calling system of the present embodiment is used to implement the foregoing method for invoking the hydro a service, the function thereof corresponds to the function of the foregoing method, and will not be described herein.
fig. 3 is a schematic structural diagram of a terminal 300 according to an embodiment of the present invention, including: a processor 310, a memory 320 and a communication unit 330. The processor 310 is configured to implement the following steps when implementing the hydra service calling program stored in the memory 320:
Packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
The application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package;
The encapsulation package reads the configured parameters mapped to the native service of the hydra;
The application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
The memory 320 may be used to store instructions for execution by the processor 310, and the memory 320 may be implemented by any type of volatile or non-volatile memory terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. The execution of the instructions in memory 320, when executed by processor 310, enables terminal 300 to perform some or all of the steps in the method embodiments described below.
the processor 310 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by running or executing software programs and/or modules stored in the memory 320, and invoking data stored in the memory. The processor may be comprised of an integrated circuit (Integrated Circuit, simply referred to as an IC), for example, a single packaged IC, or may be comprised of a plurality of packaged ICs connected to the same function or different functions. For example, the processor 310 may include only a central processing unit (Central Processing Unit, simply CPU). In the embodiment of the invention, the CPU can be a single operation core or can comprise multiple operation cores.
And a communication unit 330 for establishing a communication channel so that the storage terminal can communicate with other terminals. Receiving user data sent by other terminals or sending the user data to other terminals.
the invention also provides a computer storage medium, which can be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (random access memory, RAM) and the like.
the computer storage medium stores a hydra service calling program which when executed by the processor performs the steps of:
Packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
The application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package;
The encapsulation package reads the configured parameters mapped to the native service of the hydra;
The application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
It will be apparent to those skilled in the art that the techniques of embodiments of the present invention may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium such as a U-disc, a mobile hard disc, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk or an optical disk, etc. various media capable of storing program codes, including several instructions for causing a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the method described in the embodiments of the present invention.
In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The foregoing disclosure is merely illustrative of the preferred embodiments of the invention and the invention is not limited thereto, since modifications and variations may be made by those skilled in the art without departing from the principles of the invention.
Claims (10)
1. a method for invoking a hydro service, comprising the steps of:
Packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
The application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package;
The encapsulation package reads the configured parameters mapped to the native service of the hydra;
The application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
2. the method for invoking a hydra service according to claim 1, wherein encapsulating the configuration class of the hydra service specifically comprises:
integrating configuration classes originally required by the hydra service into codes;
The customized parameters in the configuration class are exposed to the application in the form of a configuration file.
3. the hydro a service invocation method of claim 2 wherein the encapsulated service interface comprises a core service package, an entity class, and a token handle.
4. The method of claim 3, wherein the core service package comprises a first service package and a second service package, the first service package provides a method for implementing redirection, exiting redirection, logging out, and obtaining token by callback, and the second service package provides subsequent processing logic and returned content of operation failure and success.
5. The method for invoking a hydra service according to claim 4, wherein when the service interface of the hydra service is encapsulated, the relevant interceptor extended authentication function is also written for encapsulation.
6. The hydro a service invocation method of claim 5, wherein the encapsulated interceptors include a first interceptor, a second interceptor, a third interceptor, and a fourth interceptor;
The first interceptor comprises a log recorder and provides a method for judging whether a certain URI needs to be removed, a method for judging whether a request needs to bypass OAuth authentication and a method for setting an unauthorized response state code;
The second interceptor is used for authenticating and authorizing the request of the user and providing execution logic when the authorization fails; wherein authenticating the user request includes attempting to verify whether the user's token has expired, if so, using the refresh token to refresh the token, if so, updating the user information and saving the information in the session, if so, indicating that the user request fails authentication, the request will be denied; meanwhile, storing the authentication result requested by the user into the attribute of the request;
the third interceptor is used for providing a method for judging the validity of the token and the parameters acquired from the header;
The fourth interceptor is used to check if the request has been validated by OAuth and has sufficient rights to access the request handler.
7. The method of any of claims 1-6, wherein the encapsulation packet is a starter packet.
8. A hydro-a service invocation system, characterized by comprising,
And (3) an encapsulation package construction module: packaging the configuration class and the service interface of the hydra service to construct a packaging package, and exposing the configuration file and the packaged service interface to an application program by the packaging package;
And (5) an encapsulation package calling module: the application program calls the encapsulation package, and parameter configuration is carried out by using a configuration file provided by the encapsulation package; the encapsulation package reads the configured parameters mapped to the native service of the hydra; the application program calls the relevant packaged service interface to trigger the hydra service to carry out service processing based on the service requirement.
9. A terminal, comprising:
a memory for storing a hydra service calling program;
A processor for implementing the steps of the hydro a service invocation method as defined in any one of claims 1 to 7 when executing said hydro a service invocation program.
10. A computer readable storage medium, characterized in that it has stored thereon a hydra service invocation program, which when executed by a processor, implements the steps of the hydra service invocation method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410194846.7A CN117762601B (en) | 2024-02-22 | Method, system, terminal and storage medium for invoking hydra service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410194846.7A CN117762601B (en) | 2024-02-22 | Method, system, terminal and storage medium for invoking hydra service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117762601A true CN117762601A (en) | 2024-03-26 |
| CN117762601B CN117762601B (en) | 2024-07-05 |
Family
ID=
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030046590A1 (en) * | 2001-05-18 | 2003-03-06 | Bender Michael S. | Secure personal identification number entry in a distributed network |
| US20150350212A1 (en) * | 2014-05-29 | 2015-12-03 | General Electric Company | Methods and systems for authorizing web service requests |
| CN110515848A (en) * | 2019-08-29 | 2019-11-29 | 行吟信息科技（上海）有限公司 | Automatization test system and automated testing method |
| CN112905160A (en) * | 2021-02-08 | 2021-06-04 | 中国工商银行股份有限公司 | Axios-based package registration global interception method and device |
| CN115174162A (en) * | 2022-06-17 | 2022-10-11 | 青岛海尔科技有限公司 | Authorization method, device, system and storage medium based on OAuth protocol |
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030046590A1 (en) * | 2001-05-18 | 2003-03-06 | Bender Michael S. | Secure personal identification number entry in a distributed network |
| US20150350212A1 (en) * | 2014-05-29 | 2015-12-03 | General Electric Company | Methods and systems for authorizing web service requests |
| CN110515848A (en) * | 2019-08-29 | 2019-11-29 | 行吟信息科技（上海）有限公司 | Automatization test system and automated testing method |
| CN112905160A (en) * | 2021-02-08 | 2021-06-04 | 中国工商银行股份有限公司 | Axios-based package registration global interception method and device |
| CN115174162A (en) * | 2022-06-17 | 2022-10-11 | 青岛海尔科技有限公司 | Authorization method, device, system and storage medium based on OAuth protocol |
Non-Patent Citations (2)
| Title |
|---|
| S清风S: "Ory Hydra详解之进阶", Retrieved from the Internet <URL:http://blog.csdn.cnt/u010381752/article/details/119344676> * |
| 无: "捷码科技推出自动平面布局综合产品Hydra", 电子与电脑, no. 08, 15 August 2008 (2008-08-15) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107948167B (en) | Single sign-on method and device | |
| US10484385B2 (en) | Accessing an application through application clients and web browsers | |
| US8661420B2 (en) | System and method for runtime interface versioning | |
| CN102281311B (en) | Method, system and device for implementing network service based on open application programming interface | |
| US10091179B2 (en) | User authentication framework | |
| CN109815683B (en) | Authority verification method and related device | |
| US20070006325A1 (en) | Method, system and computer program for controlling access to resources in web applications | |
| CN111782535B (en) | Test method and device | |
| CN115021991A (en) | Single sign-on for unmanaged mobile devices | |
| US9838379B1 (en) | Security tiering in a mobile communication device application framework | |
| CN105188060A (en) | Mobile terminal-oriented single sign-on (SSO) authentication method and system | |
| CN111431920A (en) | Security control method and system based on dynamic token | |
| CN110166459A (en) | A kind of means of defence and device of unserializing loophole | |
| CN111950001A (en) | Authority control method and system based on H5 application in APP | |
| CN116484338A (en) | Database access method and device | |
| CN116192483A (en) | Authentication method, device, equipment and medium | |
| CN112560006A (en) | Single sign-on method and system under multi-application system | |
| CN117762601B (en) | Method, system, terminal and storage medium for invoking hydra service | |
| US20100222022A1 (en) | Communication method, communication system and access method to service provider base | |
| CN117762601A (en) | Method, system, terminal and storage medium for invoking hydra service | |
| CN112287327B (en) | Method, device, medium and equipment for easily reconstructing single sign-on system | |
| US7020705B2 (en) | De-authenticating in security environments only providing authentication | |
| CN114924783A (en) | Interface calling method, device, equipment and storage medium of application program | |
| CN111310141B (en) | Authentication management method, device, computer equipment and storage medium | |
| CN117134927A (en) | Login verification method based on Kong gateway and related equipment |
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 |