authentik/website/integrations/documentation/glpi/index.md at e7fcfb7e67d5df3e8a8a5da170f18fa4c6b98731

mirror of https://github.com/goauthentik/authentik synced 2026-04-27 18:07:15 +02:00

Files

Teffen Ellis 6ed5cb5249 website/docs: Modal and wizard button labels (#21549 )

* website/integrations: rename "Create with Provider" to "New Application"

The application list page now uses a split-button labeled
"New Application" instead of the old "Create with Provider" dropdown.
Update all 113 integration guides to match.

* website/docs: update flow, stage, and policy button labels

- "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons
- "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit
- "Create and bind stage" → "New Stage" / "Bind Existing Stage"
- "Create" (binding submit) → "Create Stage Binding"

* website/docs: update provider button labels

- "Create" → "New Provider" for trigger buttons
- "Create with Provider" → "New Application" in RAC docs
- "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt"
  for related entity creation

* website/docs: update directory button labels

- "Create" → "New Source" for federation/social login pages
- "Create" → "New Role", submit → "Create Role"
- "Create" → "New Invitation"
- Policy binding submit → "Create Policy Binding"

* website/docs: update endpoint device and system management button labels

- "Create" → "New Endpoint Connector", "New Enrollment Token",
  "New Device Access Group", "New Flow"
- Submit → "Create Device Access Group"
- "Create" → "New Notification Rule", "New Notification Transport"
- Binding submit → "Create Policy Binding"

* Reorganize policy documentation

* website/docs: address policy docs review feedback

* post-rebase

* website/docs: Reorganize policy documentation -- Revisions (#21601)

* apply suggestions

* Fix escaped.

* Fix whitespace.

* Update button label.

* Fix phrasing.

* Fix phrasing.

* Clean up stragglers.

* Format.

---------

Co-authored-by: Dominic R <dominic@sdko.org>

2026-04-16 17:35:38 +00:00

6.8 KiB

Raw Blame History

title, sidebar_label, support_level

title	sidebar_label	support_level
Integrate with GLPI	GLPI	community

What is GLPI

GLPI (Gestionnaire Libre de Parc Informatique) is an open-source IT asset management and service desk software. It helps organizations manage hardware, software, tickets, users, and IT services in a centralized environment.

-- https://www.glpi-project.org

Preparation

The following placeholders are used in this guide:

glpi.company is the FQDN of the GLPI installation.
authentik.company is the FQDN of the authentik installation.

:::info This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application. :::

GLPI samlSSO plugin configuration

:::info By default, GLPI only offers OAuth authentication to subscribers. This guide describes how to integrate authentik with GLPI via SAML using the community plugin named samlSSO. :::

Install the samlSSO plugin

Download the latest release from the samlSSO GitHub project.
Unpack the release ZIP file into the glpi/data/marketplace directory of your GLPI installation.
Log in to GLPI as an administrator and navigate to Setup > Plugins.
Click the Install icon (folder with a + symbol) next to the samlSSO plugin.
In the pop-up window that opens, click Enable.

Add a samlSSO instance

Navigate to Setup > samlSSO.
Click the Add button and configure the following required settings:
- On the General tab:
  - Friendly name: authentik
  - Is active: toggled on
- On the Security tab:
  - Strict: toggled on
  - JIT user creation: toggled on
Click Save.
Open the authentik samlSSO instance, navigate to the Service Provider tab, and take note of the AcsUrl and sloURL. These values will be required in the next section.

authentik configuration

To support the integration of GLPI with authentik, you need to create property mappings, and an application/provider pair in authentik.

Create property mappings in authentik

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Customization > Property Mappings, click Create, select SAML Provider Property Mappings, and click Next.
Configure the first mapping for the user's given name (first name):
- Name: givenname
- SAML Attribute Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
- Friendly Name: Leave blank
- Expression:
```
return request.user.name.split(" ", 1)[0]
```
Click Finish to save. Then, repeat the process to create a mapping for the user's surname:
- Name: surname
- SAML Attribute Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
- Friendly Name: Leave blank
- Expression:
```
return request.user.name.split(" ", 1)[-1]
```
Click Finish.

Create an application and provider in authentik

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Applications and click New Application to open the application wizard.
- Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the Slug value as it will be required later.
- Choose a Provider type: select SAML Provider as the provider type.
- Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
  - Set the ACS URL to the AcsURL value from GLPI.
  - Set the Service Provider Binding to Post.
  - Set the SLS URL to the sloURL value from GLPI.
  - Under Advanced protocol settings:
    - Select any available Signing Certificate and enable Sign assertions.
    - Set NameID Property Mapping to authentik default SAML Mapping: Email.
    - Under Property mappings, add the two property mappings that you created in the previous section: givenname and surname.
- Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's My applications page.
Click Submit to save the new application and provider.

Download certificate file

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Providers and click on the name of the provider that you created in the previous section.
Under Related objects > Download signing certificate, click on Download. This downloaded file is your certificate file and it will be required in the next section.

GLPI configuration

Log in to GLPI as an administrator and navigate to Setup > samlSSO.
Click on the authentik samlSSO instance and configure the following settings:
- On the Identity Provider tab:
  - Set the Entity ID to authentik
  - Set the SSO URL to https://authentik.company/application/saml/<application_slug>/sso/binding/redirect/.
  - Set the SLO URL to https://authentik.company/application/saml/<application_slug>/slo/binding/redirect/.
  - Set X509 certificate to the contents of the certificate file that you downloaded from authentik.
Click Save to apply the changes.

JIT rules (optional)

It's possible to auto-assign profiles and groups when a user is created in GLPI.

Log in to GLPI as an administrator, navigate to Setup > samlSSO > JIT import rules, and click Add.
Provide a Name, Logical operator type, set Active to Yes, and then click Add.
Configure the following settings:
- On the Criteria tab, create a criterion to match users.
- On the Actions tab, create actions to apply to matched users.
  - You may want to add recursive=yes as an action, so that matched users have access to all entities.
Once finished, return to the Rule tab and click Save.

Configuration verification

To confirm that authentik is properly configured with GLPI, log out and click the new authentik login button on the right side. You should be redirected to authentik and once authenticated, you will be signed in to GLPI.

6.8 KiB Raw Blame History