Hi,

The idea is to make possible the activation of a captcha on the login page of GLPI.

Use an existing library (example, google recaptcha with setting the SiteKey in glpi configuration) or internal development glpi.

Regards,

Enable the option change the Login form style, Logo and Background by templates even the option out of business, in construction and so on.

When new notifications are created on a GLPI version, an upgrade to this version active these notifications.

For example, if you upgrade from 0.84 to 0.90, following notifications will be active after upgrade :

• New change
• Update change
• Resolve change
• Add task
• Update task
• Delete task
• Close change
• Delete change
• New project
• Update project
• Delete project
• Receiver Errors
• New project task
• Update project task
• Delete project task

This is the default behavior of GLPI : new notifications are active. If you don't know, our users may be surprised.

Please disable new notifications after upgrade.

There's currently no option to disable the bottom-right information pop-up that pops when you save any modification in an asset or a ticket.

This pop-up is oftentime masking other important informations/buttons and is not really useful, 99.9% of the time it only states that your modification was successful.

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