Ivanti Neurons Data Connector

The BigPanda Unified Data Connector (UDC) syncs data from Ivanti Neurons for ITSM to provide context and insights for AI Incident Assistant (Biggy), AI Incident Prevention, and AI Detection and Response. Ingested data is securely stored and made available in the IT Knowledge Graph (ITKG), powering accurate answers, deep analytics, trend analysis, and advanced capabilities.

Not bi-directional or monitoring incident sync

The Ivanti data connector does not enable incident sync or sharing from the BigPanda incident feed. The Ivanti connector extracts business object data through OData; it does not push incidents back to Ivanti.

Prerequisites

Before configuring the Ivanti Neurons connector, confirm the following with your Ivanti administrator:

An accessible Ivanti Neurons for ITSM tenant with the OData service enabled.
Credentials for one of the supported authentication strategies. See Authentication.
A list of the business objects (tables) you want to sync. The connector requires at least one business object.
For deployments where the OData service is not at the default path, the relative or absolute path to your OData root. See Custom OData path.

Time conversion

The Unified Data Connector converts all date and time fields into UTC. This ensures consistent date handling across different environments and time zones. The connector filters records using the LastModDateTime field in ISO-8601 format.

Authentication

The Ivanti connector supports four authentication strategies. Choose the one that matches your Ivanti tenant configuration. After creating the required credentials, send them to your BigPanda account team, who will finish the authorization process.

Authentication strategy	Use when
`ivanti_api_key`	Your tenant issues a long-lived REST API key for service accounts.
`ivanti_jwt`	Your tenant issues JSON web tokens (JWTs) for programmatic access.
`ivanti_session_key`	Your tenant uses session-key authentication.
`oauth2`	Your tenant delegates authentication to an external identity provider.

OAuth2 is recommended for delegated access

If your organization centralizes access through an external identity provider, use the oauth2 strategy so that BigPanda does not store long-lived Ivanti credentials.

Configure UDC with an Ivanti API key, JWT, or session key

For the ivanti_api_key, ivanti_jwt, and ivanti_session_key strategies, provide the following information to your BigPanda account team.

Field	Description
Instance	The hostname of your Ivanti tenant. For example, `<your_tenant>.ivanti.com`.
Auth strategy	One of `ivanti_api_key`, `ivanti_jwt`, or `ivanti_session_key`.
Credential	The corresponding API key, JWT, or session key value issued by your Ivanti tenant.
Time zone	The time zone of your Ivanti tenant. Used for incremental filtering.

Configure UDC with OAuth2

The oauth2 strategy delegates authentication to your external identity provider. The connector requests a token from your identity provider's token endpoint and forwards an optional scope on each authorization request.

Provide the following information to your BigPanda account team.

Field	Description
Instance	The hostname of your Ivanti tenant. For example, `<your_tenant>.ivanti.com`.
Token URL	The full URL of your identity provider's token endpoint. Required for the `oauth2` strategy.
Client ID	The client identifier issued by your identity provider.
Client secret	The client secret issued by your identity provider.
Scope	Optional. The scope value forwarded with each token request.
Time zone	The time zone of your Ivanti tenant. Used for incremental filtering.

Token URL is required

If no token URL is provided, the connector returns a missing-token-URL validation error and does not run.

Credential refresh and retry behavior

If a request returns an HTTP 401 response, the connector refreshes its credentials and retries the request once. If the retry also fails, the connector surfaces an authentication error. Repeated authentication failures in connector logs may appear after a refresh-and-retry cycle.

Custom OData path

By default, the Ivanti connector reads business objects from the standard OData collection path. For deployments with a non-standard OData root (for example, custom HEAT-style deployments), set the api_path field on the connection.

The api_path value accepts either of the following:

A relative path, for example /api/odata/custom-businessobject/.
A same-host absolute URL prefix. The host portion of the absolute URL must match the configured instance host. The connector rejects absolute URLs that point to a different host.

Same-host validation

The connector validates that any absolute api_path value resolves to the same host as the configured instance. URLs that point to a different host are rejected at configuration time.

Test the connection

After your BigPanda account team configures the connector, you can validate Ivanti reachability through the connection test flow. The connection test:

Accepts all four supported authentication strategies: ivanti_api_key, ivanti_jwt, ivanti_session_key, and oauth2.
Probes the Ivanti incidents endpoint and retrieves a single record to confirm reachability.
Reports a failure if the configured api_path is invalid, if credentials are missing or rejected, or if the OData endpoint is unreachable.

Run the connection test before scheduling a sync to confirm that the authentication strategy, instance host, and api_path work end-to-end.

Sync preferences

Provide the following information about your sync preferences to BigPanda.

Required configuration

Option	Description
`tables`	The list of Ivanti business objects to sync. The connector requires at least one business object. The connector creates one output table per business object and normalizes plural names by removing a trailing `s`.
`mode`	Determines whether the connector runs a historical or incremental sync. Most organizations use both modes on separate connectors. See the Streaming Modes documentation.
`start_date`	Required when `mode` is `historical`. The ISO-8601 date from which the connector begins filtering by `LastModDateTime`.

Optional pipeline configuration

Option	Description
`end_date`	Used for historical syncs only. The ISO-8601 date at which the connector stops filtering by `LastModDateTime`.
`cursor_field`	The field used as the incremental cursor. Defaults to `LastModDateTime`.
`page_size`	The number of records requested in a single OData page. The connector caps this value at 100; values above 100 are reduced to 100.
`request_timeout`	The number of seconds the connector waits before timing out a request.
`api_path`	The OData collection path for deployments with a non-standard root. Accepts a relative path or a same-host absolute URL prefix. See Custom OData path.

Performance-related configuration

Option	Description
`rate_limit`	The maximum number of requests the connector sends per minute.
`rate_limit_timeout_ms`	The timeout period in milliseconds after the rate limit has been reached.

Page size is capped at 100

The Ivanti connector limits OData page size to 100 records per request, regardless of the configured page_size value. Pagination uses the OData $top and $skip parameters.

Sync modes

The Ivanti connector supports two sync modes:

Historical: Filters records by LastModDateTime from start_date through end_date. Use this mode for initial backfills and one-time loads.
Incremental: Reads records modified after the last LastModDateTime cursor value. Use this mode for ongoing updates.

Most organizations configure one connector for the historical backfill and a second connector for the incremental sync. All tables in a single connector share the same sync schedule. To run different business objects on different intervals, configure a separate connector for each schedule group.

Pagination behavior

The connector iterates through OData pages using the $top and $skip parameters. Pagination ends when one of the following conditions is met:

The connector receives an HTTP 204 No Content response.
The connector receives an empty page.

Both conditions are treated as terminal pages. Empty results from a filter that matches no records are an expected outcome, not an error.

Output schema

For each Ivanti business object listed in tables, the connector produces one output table. The output schema follows these rules:

Plural business object names are normalized by removing the trailing s. For example, an incidents business object produces an output table named incident.
Each output record includes a _dlt_processing_time column that records when the connector processed the record.
All other fields from the Ivanti business object are passed through as-is.

Next Steps

Review the BigPanda Unified Data Connector overview for connector concepts shared across data sources.
See the Unified Data Connector Configuration page for shared configuration patterns.
Configure Data Redaction to protect sensitive fields before they are ingested.

In this section: