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
Custom fields query	No	—	List of custom (context) fields to request for each software record. Provide the complete context block, for example: context '{' parentPortfolio platformOwner '}'

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

Each sync is a full sync. The connector does not maintain a sync token and does not apply an incremental since filter, so every run re-fetches the complete normalized software catalog. The GraphQL query is paginated using limit and offset only.

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)*	EOL_STATUS
*(computed at sync time)*	LAST_CAPTURED
*(hardcoded)*	CATEGORIES
isOperatingSystem	IS_OPERATING_SYSTEM
lifecycle.endOfLifeDate / lifecycle.endOfLifeDateCalculated	EOL_DATE
lifecycle.obsoleteDate / lifecycle.obsoleteDateCalculated	END_OF_SUPPORT_DATE
manufacturerName	MANUFACTURER
name	UID
name	NAME
parentPortfolio	PARENT_PORTFOLIO
platformOwner	PLATFORM_OWNER
platformPointOfContact	PLATFORM_POINT_OF_CONTACT
productName	PRODUCT_NAME
softwareMarketName	SOFTWARE_MARKET_NAME
soxFlag	SOX_FLAG
technicalApplicationManagerServiceManager	TECHNICAL_APPLICATION_MANAGER_SERVICE_MANAGER
technicalSupportAnalystTechnicalApplicationOwner	TECHNICAL_SUPPORT_ANALYST_TECHNICAL_APPLICATION_OWNER
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

Not supported. The connector performs a full sync of Software on every run and applies no incremental date filter.

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
    lifecycle {
      endOfLifeDate
      endOfLifeDateCalculated
      obsoleteDate
      obsoleteDateCalculated
      generalAvailabilityDate
    }
    %s
  }
}

Changelog

Changelog

The Flexera IT Visibility connector has undergone the following changes:

Version	Description	Migration Steps
3.1.7	New Features - Added lifecycle attributes to Software records: EOL date (end-of-life), End of support date, and EOL status. The EOL status is derived from those dates as Supported, End of Life, or Unsupported. When a published vendor date is unavailable, Flexera's calculated date is used instead. - Added a Custom fields query configuration property that lets you request additional Flexera "context" fields for each Software record. You supply a GraphQL fragment (for example context { parentPortfolio soxFlag }); the fragment is injected into the software query and every field it names becomes a dynamically generated attribute. The field name is upper-snake-cased for the attribute name (e.g. parentPortfolio → PARENT_PORTFOLIO). Attributes are added only for the fields you list, and are populated only when the API returns a non-null value. Improvements - Context (ownership) attributes are no longer hardcoded. Instead of a fixed set of seven attributes that were always part of the schema (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), attributes are now derived dynamically from the Custom fields query property, so any Flexera context field can be surfaced without a code change. Because these seven attributes were populated by default in 3.1.6 but are now retrieved only when their fields are listed in the Custom fields query, existing deployments that rely on them must add the corresponding field names to the Custom fields query after upgrading, or those attributes will stop populating. - The Custom fields query is now validated at configuration time. A malformed value (missing braces, nested selection sets, comma-separated field names, trailing content after the closing brace, or field names that are not valid GraphQL identifiers) is rejected when the connector is configured, instead of producing an opaque server-side GraphQL error on every Software sync.	N/A
3.1.6	New Features - Added 7 new ownership and portfolio attributes to 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	No changes in this release.	N/A
3.1.2	No changes in this release.	N/A
3.1.1	Improvements - Renamed the connector to "Flexera IT Visibility" for clearer identification, and refreshed the connector icon. - Split connector documentation into dedicated per-connector guides for easier reference.	N/A
3.1.0	Overview The Flexera IT Visibility connector integrates with the Flexera One IT Visibility platform to synchronize the normalized software catalog as Software (Package) assets. Category: Configuration Management Models	N/A