Frequently asked questions

Download software builds from the Itential Software Repository. Contact your Itential account representative for access credentials.

Itential Platform supports the latest versions of Chrome, Firefox, and Edge.

Check the release notes for version-specific browser compatibility.

No. Itential Platform does not collect or report telemetric information.

Check your version in Admin Essentials or review the release notes for version-specific features.

Itential Platform supports:

• Bare metal servers
• Virtual machines
• Containers
• Kubernetes

See deployment architectures for requirements.

Yes. Follow the installation guide.

Platform supports:

• LDAP/OpenLDAP
• SAML SSO
• Azure EntraID
• RADIUS
• Local AAA

See authentication overview for setup.

Yes. Platform supports SAML-based SSO for on-premises and cloud deployments.

Yes. Configure granular access controls for applications, devices, workflows, adapters, integrations, and API endpoints.

Platform supports 300+ pre-built integrations for network devices, cloud platforms, and ITSM tools.

Browse integrations.

Yes. The Itential Automation Marketplace provides pre-built workflows, use cases, transformations, and documentation.

Install assets directly from Platform or download from the marketplace.

Most adapters auto-discover changes without restart. The NSO adapter reads and compiles YANG files at startup, but APIs continue working without restart.

The ServiceNow app and adapter serve different purposes:

Use both for bidirectional integration.

Requirements:

• ServiceNow instance must access Platform (direct or via MID servers)
• HTTPS protocol allowed
• Admin and user role accounts in ServiceNow
• Platform instances configured in ServiceNow

See ServiceNow app setup.

After setup:

1. Navigate to Itential section in ServiceNow
2. Select Itential Automation Services
3. Choose Platform instance and workflow
4. Complete auto-generated form
5. Submit to execute

For ServiceNow Flows, use Itential Actions in Flow Designer.

Default location: /var/log/pronghorn

If logs aren’t there, check $PRONGHORN_BASE/properties.json for custom location.

See logging overview.

Check these common issues:

• Adapter in correct namespace directory
• Dependencies installed in adapter directory
• Adapter lints clean (syntax errors prevent loading)
• Platform logs for error messages

See adapter troubleshooting.

Generate showsupport file:

$
    cd /opt/pronghorn/current
$
    ./showsupport
$
    ls -l ./showsupport*.gz

Download blueprint from Admin Essentials > Blueprints > Download.

Attach both files to your support ticket.