Skip to main content
Version: 3.0

GLPI

GLPI supports Cortex's embed URL via a custom plugin maintained by Synapse Software: https://github.com/Synapse-Software/cortex-glpi

How it works​

The plugin adds a Historical Records tab to GLPI tickets. When an agent opens a ticket, the tab renders a Cortex embed - an iframe pointed at a special Cortex endpoint that accepts context from the surrounding page.

That context is two things: the business object type (e.g. Incident) and the requester's email address. Cortex uses the email address to look up matching records in your archived data and displays them in a stripped-down grid view - no sidebar, just the data and a CSV export button.

The key requirement is that the requester's email address in GLPI matches the email address in your Cortex data. If a user exists in both systems with the same email, their historical records will appear automatically when their tickets are opened.

What the embed shows​

  • A filtered grid of records for the requester, scoped to the configured business object type
  • CSV export - every Cortex grid supports CSV export, and the embed is no exception
  • No Cortex sidebar or navigation - the view is intentionally minimal so it fits cleanly within the GLPI ticket layout

Installation​

  1. Download the latest release from https://github.com/Synapse-Software/cortex-glpi/releases
  2. Unzip the contents into your GLPI plugins directory, renaming the folder to cortex if necessary.
  3. Within GLPI, install and enable/activate the plugin.

Configuration​

  1. In GLPI's General Settings, open the Cortex Embed tab.
  2. Enter your Cortex URL - do not include /embed at the end. This should be the base URL you use to access Cortex directly.
  3. Enter the name of the business object Cortex should list. Typically this will be Incident, since the Cortex iframe appears on GLPI's Ticket form. Other valid values include HRCase, ConfigurationItem, or any other business object name in your Cortex data.

Authentication​

By default the embed relies on the agent already being logged into Cortex. JWT-based authentication - where the GLPI plugin constructs a signed token and passes identity information directly to Cortex - is planned for a future release. When available, this will allow agents to view the embed without a separate Cortex login session.

Video walkthrough​