0831715d3a
- Implement SmsService class for sending SMS via CPSMS API. - Add SMS sending functionality in the frontend with validation and user feedback. - Create database migrations for SMS message storage and telephony features. - Introduce telephony settings and user-specific configurations for click-to-call functionality. - Enhance user experience with toast notifications for incoming calls and actions.
58 lines
2.3 KiB
Markdown
58 lines
2.3 KiB
Markdown
# ESET Support Request – Full Software Inventory Access
|
||
|
||
## Background
|
||
BMC Hub can currently fetch device details from ESET Device Management, but only receives ESET component entries (typically Endpoint Security + Management Agent) via `deployedComponents`.
|
||
|
||
Goal: retrieve full installed programs list (OS-level software inventory) with version numbers per device.
|
||
|
||
## Environment
|
||
- Tenant/API base: `https://eu.device-management.eset.systems`
|
||
- IAM: `https://eu.business-account.iam.eset.systems`
|
||
- Integration uses OAuth and works for:
|
||
- `GET /v1/devices`
|
||
- `GET /v1/devices/{uuid}`
|
||
- `GET /v1/devices:batchGet`
|
||
|
||
## Observed limitation
|
||
For all tested devices in our dataset:
|
||
- `deployedComponents` contains only 1–2 ESET products
|
||
- no complete software inventory is present
|
||
|
||
Local dataset stats (sample):
|
||
- 50 devices with 2 components
|
||
- 1 device with 1 component
|
||
- 0 devices with >2 components
|
||
|
||
## Endpoint probing results
|
||
We tested candidate endpoint for software inventory:
|
||
- `GET /v1/devices/{uuid}:getSoftware` → HTTP 400
|
||
- `POST /v1/devices/{uuid}:getSoftware` → HTTP 404
|
||
|
||
No OpenAPI/Swagger endpoint was discoverable via common paths.
|
||
|
||
## Request IDs from ESET responses
|
||
Please use these IDs to trace calls in your logs:
|
||
- `7f68c8c1-1caf-4412-b57c-57735080995e` (GET :getSoftware)
|
||
- `fb367209-c619-49aa-88b4-2913802009b1` (GET :getSoftware with pageSize)
|
||
- `aab9206f-3ba2-4d1f-bb74-0fb525889c5e` (GET :getSoftware with limit)
|
||
- `6814a433-e240-4c65-b313-6cefb7c4e74d` (POST :getSoftware empty body)
|
||
- `1a261e22-8045-4b7a-a479-edecfe4e0b60` (POST :getSoftware page body)
|
||
- `ad166b80-5056-45de-9a8c-a6e8c4c2b0c2` (POST :getSoftware with deviceUuid)
|
||
|
||
## What we need from ESET
|
||
1. The correct endpoint(s) for full installed software inventory per device.
|
||
2. Required OAuth scopes/permissions/role assignments for this data.
|
||
3. Required HTTP method and request format (query/body, paging schema).
|
||
4. Confirmation whether this data is available in our tenant/region (`eu`).
|
||
|
||
## Expected response shape
|
||
We need a list like:
|
||
- app name
|
||
- version
|
||
- (optional) vendor/publisher
|
||
- (optional) install date
|
||
|
||
## Why this matters
|
||
Our UI already supports app + version table rendering, but source data is currently limited to ESET components.
|
||
Once full inventory endpoint/permissions are confirmed, we can integrate immediately.
|