Frictionless supplementary multi-factor authentication for sensitive transactions within an application session
US-2022321602-A1 · Oct 6, 2022 · US
US11579930B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11579930-B2 |
| Application number | US-202017001711-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 25, 2020 |
| Priority date | Jul 11, 2020 |
| Publication date | Feb 14, 2023 |
| Grant date | Feb 14, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one example, a computer implemented method may include retrieving resource definition data corresponding to an endpoint. The resource definition data includes resource type information. Further, an API response may be obtained from the endpoint by querying the endpoint using an API call. Furthermore, the API response may be parsed and a resource model corresponding to the resource definition data may be populated using the parsed API response. The resource model may include resource information and associated metric information correspond to a resource type in the resource type information. Further, a resource and/or metric data associated with the resource may be determined using the populated resource model. The resource may be associated with an application being executed in the endpoint.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method comprising: communicating with an endpoint by the adapter which comprises a resource transformer for retrieving resource definition data corresponding to an endpoint, wherein the resource definition data comprises resource type information, wherein the resource definition data is a template to determine at least one resource corresponding to at least one resource type; obtaining a plurality of application program interface (API) responses from the endpoint by querying the endpoint using API call; parsing the API response obtained from the endpoint; populating a resource model corresponding to the resource definition data using the parsed API response, wherein the resource model comprises resource information and associated metric information corresponding to a resource type in the resource type information; and determining a resource and/or metric data associated with the resource using the populated resource model, wherein the resource is associated with an application being executed in the endpoint; presenting the determined resource and/or the metric data associated with the resource on a graphical user interface. 2. The computer implemented method of claim 1 , further comprising: populating a relationship model corresponding to the resource definition data using the parsed API response, wherein the relationship model corresponds to the resource type; determining a relationship of the resource with another resource using the populated relationship model; and presenting the relationship on a graphical user interface. 3. The computer implemented method of claim 1 , wherein obtaining the API response comprises: generating a thread corresponding to the resource type; and executing the thread to: query the endpoint by making the API call; and obtain the API response in response to the query. 4. The computer implemented method of claim 3 , further comprising: validating transformation definitions in the resource definition data against a predefined transformation schema prior to generating the thread. 5. The computer implemented method of claim 1 , wherein populating the resource model corresponding to the resource definition data comprises: populating the resource information of the resource model in the resource definition data with the parsed API response; and applying transformation rules defined in the resource definition data to the parsed API response and/or the populated resource information to populate the metric information of the resource model. 6. The computer implemented method of claim 5 , further comprising: validating values in the parsed API response; and populating the resource model in the resource definition data using the parsed API response upon a successful validation. 7. The computer implemented method of claim 1 , wherein the resource definition data is included in a computer readable data structure, and wherein the computer readable data structure is formatted in accordance with one or more of JavaScript object notation (JSON), extensible markup language (XML), a binary file, a database file, YAML ain't markup language (YAML), and/or a proprietary encoding scheme. 8. The computer implemented method of claim 1 , wherein the resource definition data comprises an API call address to make the API call to the endpoint. 9. The computer implemented method of claim 1 , wherein the resource definition data comprises a reference to an API call address that is located in an external source, wherein the API call address is used to make the API call to the endpoint. 10. The computer implemented method of claim 1 , wherein the endpoint comprises a collection of servers and applications that work together at a production phase, the applications being accessible to one or more users. 11. A management node comprising: a processor; and memory coupled to the processor, wherein the memory comprises: an adapter to communicate with an endpoint, the adapter comprising: a resource transformer to: retrieve resource definition data corresponding to the endpoint, wherein the resource definition data comprises resource type information, wherein the resource definition data is a template to determine at least one resource corresponding to at least one resource type; and a resource manager to: obtain a plurality of application program interface (API) responses from the endpoint by querying the endpoint using an API call; parse the API responses obtained from the endpoint; and populate a plurality of resource models corresponding to the resource definition data using the parsed API responses, wherein each of the resource models comprises resource information and associated metric information that correspond to a resource type in the resource type information; and a resource extractor to: determine a plurality of resources and/or metric data associated with the resources using the populated resource models; wherein the resource extractor is to: present the plurality of resources and/or the metric data associated with the plurality of resources on a graphical user interface, wherein the resources are associated with one or more applications being executed in the endpoint. 12. The management node of claim 11 , wherein the resource extractor is to: populate a relationship model corresponding to the resource definition data using the parsed API responses, wherein the relationship model corresponds to the resource type; determine a relationship between the plurality of resources using the populated relationship model; generate a resource topology corresponding to the endpoint using the determined relationship between the plurality of resources; and present the generated resource topology on a graphical user interface. 13. The management node of claim 11 , wherein the resource manager is to: generate a thread pool with each thread in the thread pool corresponding to a resource type in the resource definition data; and execute the thread pool such that each thread is to obtain a corresponding API response by querying the endpoint by making the API call. 14. The management node of claim 11 , wherein the resource manager is to: populate the resource information of the plurality of resource models in the resource definition data with the parsed plurality of API responses; and apply transformation rules defined in the resource definition data to the parsed plurality of API responses and/or the plurality of populated resource information to populate the metric information. 15. The management node of claim 11 , wherein the endpoint comprises one of a physical computing environment, a cloud computing environment, and a virtual computing environment. 16. A non-transitory machine-readable storage medium encoded with instructions that, when executed by a computing device, cause the computing device to: communicating with an endpoint by the adapter which comprises a resource transformer to retrieve resource definition data corresponding to an endpoint from an adapter of the computing device, wherein the adapter is to enable communication with the endpoint, wherein the resource definition data comprises resource type information, and wherein the resource definition data is a template to determine at least one resource corresponding to at least one resource type; generate a thread corresponding to a resource type in the resource type information; execute the thread to obtain a plurality of application program interface (API) responses by querying the endpoint using an API call; parse the API response obtained from the endpoint; populate a resource model correspon
Entity relationship models · CPC title
Monitoring of software · CPC title
the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title
where the computing system component is a software system · CPC title
Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs (verification or detection of system hardware configuration G06F11/2247) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.