Flexera IT Visibility

Configuration Management

Overview

The Flexera IT Visibility (ITV) connector integrates with the Flexera One IT Visibility platform and synchronizes normalized software catalog data. It retrieves the software titles that Flexera has recognized and normalized across the environment and maps them into Brinqa as Package records. Data is read from the Flexera IT Visibility GraphQL API.

Data retrieved from Flexera IT Visibility

Connector Object	Required	Maps to Data Model
Software	Yes	Package

note

For detailed steps on how to view the data retrieved from Flexera IT Visibility in the Brinqa Platform, see How to view your data.

Setup

Connection settings

When setting up a data integration, select Flexera IT Visibility from the Connector dropdown and provide the following:

Setting	Required	Default	Description
API URL	No	—	API URL
Login URL	No	—	IT Visibility authentication URL
Organization ID	No	—	IT Visibility organization ID
Refresh token	No	—	IT Visibility refresh token
Page size	No	—	Maximum number of records to get per API request

Authentication

The connector authenticates with Flexera using an OAuth2 refresh token grant. The configured refresh token is exchanged for a short-lived Bearer access token, which is then sent on every GraphQL request. The access token is cached and automatically refreshed when it is near expiry.

Token Endpoint

Method	URL
POST	https://login.flexera.com/oidc/token (configurable via the Login URL property)

Request Headers

Header	Value
Content-Type	application/x-www-form-urlencoded

Request Body (form-encoded)

Parameter	Value
grant_type	refresh_token
refresh_token	the configured refresh token

Sample Response

{
  "access_token": "",
  "expires_in": 3600,
  "refresh_token": "",
  "token_type": "Bearer"
}

Response Fields

Field	Description
access_token	The bearer access token used to authorize subsequent API requests.
expires_in	Lifetime of the access token in seconds. The connector refreshes the token before it expires.
refresh_token	Refresh token returned by the provider.
token_type	Token scheme, Bearer.

Using the Token

Subsequent GraphQL requests include the token in the Authorization header as Bearer <access_token>. GraphQL queries are issued via POST to:

https://api.flexera.com/graphql/v1/orgs/{orgId}/graphql

Sync Behavior

The connector supports incremental (delta) syncs. It maintains a sync token between runs and applies it as an incremental timestamp filter, so each run re-processes only the records that changed after the previous sync. The initial run retrieves the complete data set; later runs are incremental. The specific timestamp field applied to each object is documented under that object's Sync Duration Parameter.

How to obtain Flexera IT Visibility credentials

Obtain a Flexera API refresh token

For the Flexera IT Visibility connector to access the Flexera API, you must provide an API refresh token. To do so, follow these steps:

1. In your web browser, go to the appropriate login URL based on your region, and log in to your organization's FlexeraOne account:

   • North America: app.flexera.com
   • Europe (EU): app.flexera.eu
   • Asia-Pacific (APAC): app.flexera.au

2. In the top-right corner of the page, click your profile icon, and then select User Settings from the dropdown.

3. In the left-hand navigation menu, click API Credentials, and then click Create API Refresh Token.

   Your new refresh token displays. You cannot view the token again after this. Copy and save it to a secure location.

4. Click Close.

Note: If you do not have permission to generate a refresh token, contact your Flexera administrator. For additional information, see FlexeraOne documentation.

Data & mappings

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Software

Source Field Name	SDM Attribute
*(computed at sync time)*	LAST_CAPTURED
*(hardcoded)*	CATEGORIES
context.parentPortfolio	PARENT_PORTFOLIO
context.platformOwner	PLATFORM_OWNER
context.platformPointOfContact	PLATFORM_POINT_OF_CONTACT
context.softwareMarketName	SOFTWARE_MARKET_NAME
context.soxFlag	SOX_FLAG
context.technicalApplicationManagerServiceManager	TECHNICAL_APPLICATION_MANAGER_SERVICE_MANAGER
context.technicalSupportAnalystTechnicalApplicationOwner	TECHNICAL_SUPPORT_ANALYST_TECHNICAL_APPLICATION_OWNER
isOperatingSystem	IS_OPERATING_SYSTEM
manufacturerName	MANUFACTURER
name	UID
name	NAME
productName	PRODUCT_NAME
versionName	CURRENT_VERSION

Operations & API

Operations & API

Expand each connector object to see its operation options, delta-sync behavior, and the API it uses. See connector operation options for how to apply operation options (keys and values are case-sensitive).

Software

Operation options

This object does not support any operation options.

Delta sync

Supported.

API

• Type: GraphQL query · Endpoint: POST https://api.flexera.com/graphql/v1/orgs/{orgId}/graphql
• Default filters: none — the full normalized software catalog is retrieved on each sync

query ($limit: Int, $offset: Int) {
  software(limit: $limit, offset: $offset) @flatten @distinct {
    isOperatingSystem
    lifecycleId
    majorVersionId
    manufacturerId
    manufacturerName
    marketVersionId
    name
    productId
    productName
    versionName
    context {
      parentPortfolio
      platformOwner
      platformPointOfContact
      softwareMarketName
      soxFlag
      technicalApplicationManagerServiceManager
      technicalSupportAnalystTechnicalApplicationOwner
    }
  }
}

Changelog

Changelog

The Flexera IT Visibility connector has undergone the following changes:

Version	Description	Migration Steps
3.1.6	New Features - Added 7 new ownership and portfolio attributes to IT Visibility Software records: Parent Portfolio, Platform Owner, Platform Point of Contact, Software Market Name, SOX Flag, Technical Application Manager / Service Manager, and Technical Support Analyst / Technical Application Owner. These attributes are sourced from the Flexera context ownership data. Improvements - Removed the Source Created Date attribute from the Software model schema, as it was registered but never populated from the API.	N/A
3.1.5	New Features - Added a Last Captured timestamp to Software records, indicating when each record was last synchronized. Improvements - Software records with missing or blank names are now gracefully skipped instead of causing sync failures. - Duplicate software records returned by the Flexera API are now automatically deduplicated during sync.	N/A
3.1.4	Improvements - Internal release and build pipeline maintenance. No functional changes to data collection or models.	N/A
3.1.3	Bug Fixes - Corrected the CVSS v4 base score on Vulnerability Definition records. Previously the connector populated the CVSS v4 base score field with the CVSS v3 score; it now stores the correct CVSS v4 value. Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	• Vulnerability Definition: The CVSS v4 base score value now reflects the correct source value rather than the CVSS v3 score. Action: re-sync the connector so existing records are updated with corrected scores.
3.1.2	New Features - Added CVSS v4 support to Advisory and Vulnerability Definition records, including the CVSS v4 base score, vector string, and derived CVSS metrics.	• Vulnerability Definition: The Threat Score attribute changed from a text value to a numeric (decimal) value. Action: re-sync the connector so existing records store Threat Score in the new numeric type.
3.1.1	Improvements - Renamed the connectors to "Flexera Software Vulnerability Research" and "Flexera IT Visibility" for clearer identification, and refreshed the connector icons. - Split connector documentation into dedicated per-connector guides for easier reference.	N/A
3.1.0	New Features - Added the Flexera IT Visibility connector, which integrates with Flexera IT Visibility to synchronize installed software inventory as Software assets. Improvements Dependency Upgrades - Upgraded internal framework and model libraries to the latest stable versions for improved reliability, security patches, and alignment with the rest of the connector platform.	N/A
3.0.3	Improvements - Refined attribute typing for more accurate reporting: Product Release "End of life" is now a true/false value, Product Release "Vendor name" is stored as text, and Advisory "Source severity" is stored as a numeric value.	• Product Release: The "End of life" attribute changed from text to a true/false value and the "Vendor name" attribute changed to text. Action: re-sync the connector so existing records store these attributes in their corrected types. • Advisory: The "Source severity" attribute changed to a numeric value. Action: re-sync the connector so existing records store the corrected type.
3.0.2	Improvements - Vulnerability Research now requests only Cpe Record entries modified since the last run during incremental syncs, reducing sync time and load on the Flexera API.	N/A
3.0.1	New Features - Added the Cpe Record model, which synchronizes CPE (Common Platform Enumeration) product entries from Flexera Software Vulnerability Research.	N/A
3.0.0	Overview The Flexera Software Vulnerability Research connector integrates with Flexera Software Vulnerability Research to synchronize security advisories, vulnerability definitions, and the affected products, releases, and vendors they reference. Category: Vulnerability Management Models	N/A