LogoLogo
DownloadGLPI ChangelogPricesGLPI Webiste45-day free trial
  • Welcome
  • FAQ
  • FAQ Plugins
  • Tutorials
  • Videos
  • Most popular
    • Setting up Oauth IMAP Entra
    • Customise my logo
    • Setting up Oauth SMTP Entra
  • Account and subscription
    • Subscribe to GLPI cloud
  • Authentication
    • Activate sso
    • Authenticate with local LDAP
    • Integrate GLPI Network Cloud and LDAPS (Entra)
    • Setting up LDAP
  • Automatic actions
    • Setting up automatic actions
    • Check automatic actions
  • General
    • Setting up your calendar
    • Managing dashboards
    • Fields unicity
  • Helpdesk
    • Add a task
    • Add changes
    • Creating ITIL Category
    • Add an external planning
    • Managing problems
    • Add a pending reason
    • Creating Templates for Tickets
    • Using survey satisfaction
    • Setting up Service levels (SLA)
  • Inventory
    • Using blacklist
    • Collect Data
    • Inventory Android smartphones
    • Computer inventory
    • Deploying agents via GPO
    • Deploy via GlpiInventory
    • Using impact analysis
    • Installing the GLPI agent Toolbox
    • Setting up mirror servers
    • Setting up remote inventory
    • Securing exchanges between GLPI agents <-> GLPI server
    • Inventory printers and network hardware
  • Knowledge
    • Overview
    • Search engine
  • My instance
    • Customise my logo
    • Final migration
    • Export local database
    • Export my data
    • Find out my address
    • Migrate my existing GLPI on GLPI Network Cloud
    • Privacy policy and GPRD
    • Rename my instance
    • Slowdown on my instance
  • Notifications
    • Setting up Oauth SMTP Entra
    • Oauth SMTP Google
    • Setup notifications
    • Reminders
  • Plugins
    • Install and update plugins
    • Marketplace
  • Procedures
    • Apply patch
    • Free up space on your database
    • Install GLPI on Ubuntu
    • Use Percona's tools for large GLPI databases
    • Registration key marketplace
  • Receivers
    • Setting up OAuth IMAP Google
    • Setting up receiver and tickets
    • Collect emails from Gmail
    • Setting up Oauth IMAP Entra
    • Receiver iCloud
    • Receiver and delegating mailboxes
    • Receiver Office365
  • Rules
    • Authorizations rules
    • Business rules for tickets
    • Rules engine and dictionaries
  • Tools
    • Manage your projects
    • rssfeed
Powered by GitBook
LogoLogo

Social Media

  • GitHub
  • Instagram
  • LinkedIn
  • Facebook
  • Youtube
  • X
  • Reddit
  • Telegram

Category

  • FAQ
  • FAQ Plugins
  • Tutorials
  • Videos

Ressources

  • Download
  • GLPI Changelog
  • Prices
  • GLPI Website
  • 45-day free trial

©2025 - Teclib

On this page
  • Criteria
  • Actions
  • References

Was this helpful?

Edit on GitHub
Export as PDF
  1. Rules

Authorizations rules

In this article, we will see how to define a Rule to assign an authorization to a user coming from an LDAP source automatically.

Reminder

  • A Rule is the combination of Criteria and Actions, actions will be triggered if the criteria are met.

  • A rule is defined by its logical operator: AND or OR.

    • AND = All criteria must be met

    • OR = One of the criteria must be met

  • The rules engine for entitlements runs ALL rules. So pay attention to their consistency / order.

  • To define a rule, go to the menu Administration > Rules> Rules for assigning authorizations to a user.

  • Add a new rule by clicking on add

Criteria

It is necessary to define one or more criteria. In our case we have to tap on the LDAP criteria.

GLPI allows you to select multiple LDAP attributes, for example:

  • MemberOf;

  • Email;

  • TelephoneNumber;

  • User ID;

  • Common Name;

  • etc.

Once your criteria has been selected, you must define how GLPI should take this criteria into account by defining an operator, for example:

  • is;

  • contains;

  • finished by;

  • exists;

  • does not exist;

  • etc.

Let´s take a specific case. I want to establish a rule for my users who are members of a group containing the term SECURITY in the name.

  • My criteria therefore will be MemberOf and the action will be contains.

  • Then I enter the value of my criteria. Here it will be SECURITY.

Actions

Reminder:

An authorization is the combination of the following three concepts:

  • User;

  • Profile;

  • Entity.

Example :

User
Profile
Entity

John

technicien

Infrastructure

Transformed into an enabling rule:

  • Criteria = User

  • Actions = Entity + Profile

Our criteria being defined, we can now create at least two actions necessary to affect a profile and an entity.

GLPI also allows you to influence on other objects or user status, for example:

  • Active ( yes or no );

  • Recursive (yes or no );

  • Default entity;

  • etc.

At this step our rule is functional.

Users with SECURITY in their MemberOf attribute will be Technician in the Infrastructure entity.

To know

The rule will be applied when users log in or at each LDAP synchronization with GLPI.

References

PreviousRulesNextBusiness rules for tickets

Last updated 2 months ago

Was this helpful?

Documentation GLPI "Users profiles"
Alt text
Alt text