Integrations GLPI documents in its core and its plugins: identity providers, mail services, device management tools, monitoring, outbound webhooks and the OAuth2 API.
Signing users in to GLPI with Entra ID, Okta, Google or Keycloak through the OAuth SSO plugin and provisioning them with the SCIM plugin: subscription requirements, public versus private URL rules, external authentication settings, attribute mapping and password sync limits.
Keeping email-to-ticket working against Microsoft 365 and Gmail with the OAuth IMAP plugin: why basic authentication collectors stop, Entra app registration or Google client setup, offline tokens that renew automatically, and OAuth SMTP for outbound notifications.
Bringing Macs, iPhones and iPads managed in Jamf Pro into the GLPI inventory with the Jamf plugin: object mapping to computers, phones and software, synchronized hardware, OS, warranty and security state, user mapping and extension attributes.
Feeding computers managed by Microsoft System Center Configuration Manager into GLPI with the SCCM plugin: the collect and push automatic actions, SQL Server driver prerequisites, the FusionInventory dependency, collected data, and when GLPI Agent is the better route.
Sending GLPI events to chat, billing or automation systems with GLPI 11 webhooks: itemtype and event triggers, entity scope, filters such as critical tickets only, custom payloads and headers, retries, response logging and its database cost.
Building integrations on GLPI's RESTful API v2: registering OAuth clients, password versus authorization code grants, scopes including inventory and GraphQL, token lifetime settings, and when the legacy API is still needed.
Showing Centreon host and service status inside GLPI assets with the Centreon plugin: API connection settings, matching items present in both tools, acknowledging problems, scheduling downtime and triggering checks from GLPI.
Adding Okta, Google or Keycloak sign-in buttons to GLPI with the OAuth SSO plugin: GLPI Network subscription requirement, automatic user creation, forced SSO and profile assignment by rules.
When SAML is mandatory: the community SAMLSSO plugin for GLPI 11, replacing the deprecated GLPI SAML plugin, multiple identity providers and login strategies, and its support model.
Sending GLPI notifications through Microsoft 365 or Gmail with SMTP plus OAuth instead of basic authentication: the Entra app registration, callback URL and client secret expiry to track.
Choosing between GLPI's legacy REST API and the OAuth2-only High-level API v2 for integrations, and planning the move of existing scripts and connectors to v2.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.