For example, gather every computer in a group that has Google Chrome installed. Seems to be impossible at the moment (GLPI 10.0.17).

Hi!

I would like to propose the addition of a feature that allows users to log in and register to the GLPI system using Azure AD B2C. This integration could significantly streamline the onboarding process for new users.

Benefits:

• Faster User Integration: By enabling Azure AD B2C integration, organizations can quickly onboard new users without the need for manual account creation. This can greatly speed up the process and reduce administrative overhead.

• Domain-Based User Validation: The system could validate new users based on the domain configured in the client’s entity. This ensures that only users from allowed domains can register and log in, enhancing security and control.

• SSO Configuration: This feature would facilitate the configuration of Single Sign-On (SSO) without the need to register an enterprise application for each client tenant. This can simplify the setup and maintenance of SSO across multiple client environments.

Why This Solution is Beneficial:

Current solutions require adding login buttons for each registered enterprise application through which users authenticate into GLPI. This means that every new user must select the button corresponding to their organization, potentially revealing the list of organizations with which we collaborate.

Integrating Azure AD B2C addresses this issue. Users can log in seamlessly using a unified method, without needing to see or select between different organizational buttons. This enhances both security and user experience by keeping organizational details concealed and simplifying the login process.

Implementing this feature would provide a more modern and efficient user management experience within GLPI, aligning with current best practices in identity management.

Marcin

Add a different smtp server per entity in order to send email notification on différents domains.

For example: A common GLPI server for two companies with differents domains

Best regards

In addition to the top view of the server room, the possibility of seeing a complete row of racks, like the simple view of a rack but with all the storage.

I have not seen any tickets related to depreciation support. I really enjoy working with GLPI, but one of features that I think would be very useful is the incorporation of depreciation. Many ITSM projects incorporate some sort of straight line depreciation reporting. It looks like this was brought up in 2010 https://forum.glpi-project.org/viewtopic.php?id=21692

This would be a great feature in the Management field with either "Depreciation Rate" or set the rate based on asset type like "Computers - 5 year depreciation"

It would be nice to then pull reports on current assets values. Let me know if I'm missing some configuration, but based on my testing there is only currently Amortization support.

A computer (any type of asset) can be addressed through a unique url, something like http://localhost/glpi-9.2.4/front/computer.form.php?id=4150, where 4150 is the (unique, internal) id of the computer.

I'd like to use a url where the parameter is the inventory number (supposed unique)

It would be great to have possibility to fix a connection resource as default to users... now, first option is internalDB, but we use LDAP, so users have to change it manually (and some of them don't do it...).

Technicians shouldn't see the satisfaction information of the tickets to avoid some problems between requesters and technicians. 

Maybe some right rules for the satisfaction on Profiles since the managers should see these informations.

The current behavior:

When a major incident occurs, we receive a lot of call. The best practice is to create a ticket for the first caller and add each next callers as requester to this ticket.

Today GLPI allow to setup the sending of a notification to the “requester” based on the event “ticket creation”. Which means that the first user receive a notification.

GLPI allow also to setup a notification to the “requester” based on the event “New user in requesters” but this means that

• When adding user 2, the users 1 receives a second notification and the users 2 receives a first notification.
• When adding user 3, the users 1 receives a third notification, the users 2 receives a second notification and the users 3 receives a first notification.
• And so on…, when adding 20 users to a ticket, the user 1 receive 21 notifications…

As a consequence, we may not setup the notification to added users based on the event "new user in requesters"... Only the first user is notified.

The good news is that it is already possible today to send a notification automatically to each caller when the technician solve the incident.

My idea:

by adding a recipient “last requester added" to the recipient’s notification, we would be allow to send a notification to the added users only.

In this way, each users would be informed once when calling.

Merci à Jean-Mathieu, Julien et Bazile et tous les contributeurs pour GLPI :) and thank you for reading me.

Malamort

on GLPI 9.2  

Hello! Thank you very much for GLPI! Add please the function of moving the equipment between types. The fact is that when you create equipment in the "equipment" then it is impossible to move to the "printers" tab. Thank you.