Universal REST API Fetcher
Universal REST API Fetcher provides a generic interface to fetch logs from cloud sources via REST APIs. The cloud sources can have multiple endpoints, and every configured source consumes one device license.
Package Details
- Fetcher
- UniversalRestApi
Enhancements
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| URAF now supports relative URLs for Next Page requests in response headers for consistent log fetching. |
PLUG-16328 |
89114, 89434 |
| URAF now parses unique JSON Content-Types, for example: application/hal+json for improved compatibility with APIs. |
PLUG-16293 PLUG-16327 |
89114, 89202 |
Bug Fixes
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| In some cases, log fetching stopped unexpectedly without error messages, which led to missed alerts. |
PLUG-13303 |
85991, 86858, 86923, 89196, 89680, 90080 |
| After upgrading to Director Console v2.7.0, URAF-based Logsource Templates did not work with Logpoint 7.6.0. |
PLUG-16478 |
90138 |
Known Issue
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| After upgrading to Director Console v2.7.0 with Logpoint v7.6.0, URAF logsource templates are only listed after you perform a sync operation in the respective Logpoint. |
PLUG-16478 |
Past Releases
Universal REST API Fetcher v3.2.0
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| The Oauth 2.0 Password Credentials grant type now supports Client Secret as an optional field for vendors that require it. |
PLUG-10998 |
79328 |
| In Endpoints, users can reset checksum values if required using the new Reset button. |
PLUG-15626 |
- |
Bug Fixes
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| If the Initial Fetch date was edited, Universal Rest API fetcher failed to fetch logs from that new updated date. |
PLUG-13284 |
86087 |
| Editing log sources created in URAF 2.1.1 after upgrading to version 2.2 displayed errors in charset and when updating new proxy IP and port. |
PLUG-11926 |
83724, 83879 |
| In Authorization Type API Key, the API Key Prefix field was not optional. |
PLUG-10877 |
78008, 84008 |
| When one or more log sources were configured, an interruption in the log collection service resulted in the loss of logs being fetched during that session. |
PLUG-11778, PLUG-11994, PLUG-11779 |
83879 |
Universal REST API Fetcher v3.1.0
Version: 3.1.0
Release date: 30th October, 2024
Supported On: Logpoint v7.4.0 and later
Documentation: Universal REST API Fetcher Guide
SHA 256: 98d1ed1322fd1583c42481fe569b3e84a6ca2af5e3bb0a7ea58836b23e1687b2
Enhancement
Universal REST API Fetcher now supports:
| Description | Issue ID | Reference ID |
|
Universal REST API is now compatible with Logpoint v7.5.0. |
PLUG-11838 |
Universal REST API Fetcher v3.0.0
Version: 3.2.0
Release date: 2024-04-24
Supported On: Logpoint v7.4.0 and later
Documentation: Universal REST API Fetcher Guide
SHA 256: 19533e6e6eabde9f75b221130411866a59009dd9bc5b3484dcf49401e2f1663a
Enhancement
Universal REST API Fetcher now supports:
| Description | Issue ID | Reference ID |
|
Response handler that is responsible for processing the raw responses received from RESTful APIs, parsing and transforming them into a format that Logpoint can understand. |
PLUG-10586 | |
|
All time zones. You can see and select the list of the time zones while configuring the fetcher if the event time is not in UTC. |
PLUG-10567 | 76506 |
Universal REST API Fetcher v2.2.0
Release version: 2.2.0
Release Date: October 04, 2023
Supported On: Logpoint v7.3.0 and later
Download: UniversalRestAPI_2.2.0.pak
SHA256: 20d4c4c1fcc077a266aade27a44faa4e12e9e13a251a8d5dd865a504f576149b
Documentation: Universal REST API Fetcher Guide
Enhancement
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| Universal REST API is now compatible with Logpoint v7.3.0. | PLUG-10722 | - |
Universal REST API Fetcher v2.1.1
Release version: 2.1.1
Release Date: September 05, 2023
Supported On: Logpoint v7.2.0 and later
Download: UniversalRestAPI_2.1.1.pak
SHA256: 25aba169cbbd38896bd38abcfb2832cb05049d7a33722ba708fd903b29c2eaa5
Documentation: Universal REST API Fetcher Guide
Enhancements
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| You can now use the OAuth 2.0 Password credentials as a grant type for authentication. | PLUG-10372 | 74291 |
|
You can now specify the POST request's body. Also, both the body and query filtering parameters currently use the Jinja template to configure start and end values. |
PLUG-10410 | 75965 |
| You can now do multiple configurations for the same endpoint, but the name must be different. | PLUG-10387 |
Bug Fixes
The following issues are fixed:
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| Universal REST API Fetcher was not able to find the correct incremental value if the logs were in Nested format. | PLUG-10499, PLUG-10432 | 76016, 76181 |
| The Custom Date Format placeholder was displaying yyyy-mm-dd instead of %Y-%m-%d. | PLUG-10332 | - |
Universal REST API Fetcher v2.1.0
Release version: 2.1.0
Release Date: June 09, 2023
Supported On: Logpoint v7.2.0 and later
Download: UniversalRestAPI_2.1.0.pak
SHA256: 12071ddcd7dfd18caea91109e256d8717081a5e0d470684c6d5b040558c814ae
Documentation: Universal REST API Fetcher Guide
Enhancements
|
Description |
Issue ID |
Reference ID |
|---|---|---|
| Universal REST API Fetcher now supports the OData query filter. Go to Universal REST API Fetcher Guide for details. | PLUG-9846 | - |
|
Universal REST API Fetcher now supports integrations that have custom authentication mechanisms and request handling, such as DUO Security and Cybereason. |
PLUG-9717, PLUG-9577 | - |
| Users can now specify the response key, which is an identifier to locate and parse logs within an API response. Go to Universal REST API Fetcher Guide for details. |
PLUG-9740 |
Bug Fixes
The following issues are fixed:
|
Description |
Issue ID |
Reference ID |
|---|---|---|
|
Universal REST API Fetcher retrieved duplicate logs if the logs filtering parameter was set to Unique ID. |
PLUG-9206 | 68967 |
| Universal REST API Fetcher was not able to fetch logs if log filtering parameters and incremental keys were in different formats. | PLUG-9490 | 70618, 72395 |
If you have any questions or require assistance, create a support ticket.
Comments
Article is closed for comments.