Authorizations assignment rules
User Rights Assignment Rules
GLPI's rights assignment rules allow for the automation of user access and role management during their connection or synchronization with the directory (LDAP / Active Directory, SCIM, etc.).
Main Benefits:
Lifecycle Automation: They instantly assign the correct profile (e.g., Self-Service, Technician, Admin) and entity upon the user's first login, eliminating manual entry.
Security and Compliance Guarantee: By directly leveraging attributes or groups from your corporate directory, they ensure that each employee has precisely the rights corresponding to their role.
Reduced Administrative Overhead: They prevent GLPI administrators from having to manage rights on a case-by-case basis, while also ensuring automatic profile updates in case of department changes or departures.
Default Profile
If a default profile is defined in the GLPI profile configuration, and if a rights assignment rule does not include a profile assignment, then the default profile is used when assigning a user to an entity.
If no default profile is defined, the user is imported without rights: they are neither assigned to an entity nor a profile. Only the super-admin profile can see them in the root entity.
Permissions Based on Mail Server
IMAP mail information can be used to automatically assign permissions. The IMAP identifier (user login) and the mail server URL can be used as criteria. Users can be created on the fly during their login. However, it is not possible to perform a bulk import from the mail server.
Permissions Based on Mail Server URL
When multiple mail servers are defined as authentication sources and the mail server URL is a relevant criterion, this information can be used to define permissions.
Permissions Based on Mail Identifier
When user email addresses contain multiple domain names, or information relevant for defining permissions, this information can be used to define permissions. It is also possible to assign an entity to a user using the mail domain if it is specific to an entity. The mail domain used by the entity is defined in the advanced entity information.
Permissions Based on LDAP Directories
An LDAP attribute of a user can be used as a source to dynamically assign permissions to that user using permission assignment rules. There are many ways to use an LDAP tree to create authorization rules for users, with the best solution depending on the context of the directory implementation.
Permissions Based on LDAP Directory Organizational Units
Given an LDAP directory where the organization of branches (organizational units) corresponds to the organization of GLPI entities. Each organizational unit (ou) contains users, either directly or in a sub-branch. Each of these branches can be used to establish a rule for assigning a user to an entity. The case of users belonging to multiple entities must be handled elsewhere. This model is relevant when a default profile can be assigned to the majority of users. The assignment of non-standard profiles must be handled elsewhere. The user information sent by the directory is sufficient to create the assignment rules in GLPI.
Group or User Attribute-Based Authorizations in an LDAP Directory
In the directory, each user belongs to a group corresponding to a GLPI profile and a group corresponding to an entity. A user can belong to multiple profiles and multiple entities. Depending on the directory configuration, information about the user's group membership can be found in the user object or in the group object.
In the first case, the information contained in the user object is sufficient to create authorization rules: it is not necessary to import the directory groups into GLPI.
In the second case, the information contained in the user object is not sufficient, and it is necessary to retrieve group information. You must first configure LDAP groups and automatic user-group linking.
Using Different Authorization Sources
Mixed scenarios can occur: rules can use both organizational unit membership for entity assignment and group membership for profile assignment.
Available Criteria
LDAP Directory
LDAP directory configured in GLPI
LDAP_SERVER
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
E-mail entered in the user profile
MAIL_EMAIL
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
Group
User present in the group
_groups_id
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regular expression does not match, exists, does not exist, is under, is not under
Identifier
User login identifier
LOGIN
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
Mail Server
Connection type via a mail server configured in GLPI
MAIL_SERVER
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
Authentication Type
One of the connection types present in GLPI (internal database, external authentications, mail server, etc.)
TYPE
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
(AD) User ID
User ID present in LDAP
samaccountname
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
(LDAP) Memberof
Member of an LDAP group
memberof
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
(LDAP) Title
User's title
title
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, is under, is not under
(LDAP) Common Name
User's name in LDAP
cn
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) Department Number
Department number present in LDAP
departmentnumber
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) DistinguishedName
Alias present in LDAP
dn
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) Email
Email present in LDAP
mail
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP)Emplyee Number
User's employee number
employeenumber
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) Manager
User's manager declared in LDAP
manager
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) Organisation
Organization entered in the user's LDAP record
o
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) Telephone Number
User's telephone number present in LDAP
phone
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(LDAP) User ID
User ID present in LDAP
uid
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
(SCIM)homePhone
Phone number present in the SCIM server user record
TODO
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
Object Class
Ensure the authorization rule applies only to the correct LDAP directory object type (example: **user**, **group**, **computer**, etc.)
objectclass
is, is not, contains, does not contain, starting with, finished by, regular expression matches, regex does not match, exists, does not exist, under, not under
Available Actions
Skip remaining rules
_stop_rules_processing
assign
Entity
entities_id
assign
Entity from LDAP information
_affect_entity_by_dn
assign
Entity from TAG
_affect_entity_by_tag
assign
Entity from email domain
_affect_entity_by_domain
assign
Entity from full name
_affect_entity_by_completename
assign
Profiles
profiles_id
assign
Recursive
is_recursive
assign
Enabled
is_active
assign
Ignore import
_ignore_user_import
assign
Default entity
_entities_id_default
assign
Groups
specific_groups_id
assign
Default group
groups_id
assign
Timezone
timezone
assign
Language
language
assign
Deny login
_deny_login
assign
Last updated