centreon / .github Goto Github PK

License: Apache License 2.0

.github's Introduction

Centreon - IT and Application monitoring software

Introduction

Centreon is one of the most flexible and powerful monitoring softwares on the market; it is absolutely free and Open Source.

Getting Started

Centreon software can be set up

Using the sources
Using the packages
Using the ISO
Using the VM (tutorial available on Youtube)

Supported versions

Regarding the Products Lifecycle Policy, only the following versions are supported:

Centreon 21.10.x, released on November 2, 2021, full support
Centreon 21.04.x, released on April 21, 2021, security and blocking issue support only
Centreon 20.10.x, released on October 21, 2020, security support only

If your version is not one of the 3 versions specified above, we recommend that you upgrade your platform immediately.

Authors

Project leaders

Product managers

Development team

Quality Assurance

Documentation

See also the list of our contributors

Security Acknowledgement page

We want to thank all reporters and pentesters who help us improve our product each day.

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, bug report, feature request and the process for submitting pull requests for us.

License

This project is licensed under the Apache 2.0 License - see the LICENSE.md file for details

.github's People

Contributors

Watchers

Forkers

ponchoh gg0h

.github's Issues

.github repository name prevent synchronization with GitLab

As Centreon is member of OW2, we setup (for source code archiving purpose) a synchronization between Centreon organization on GitHub and a centreon group on OW2 GitLab.
Sadly GitLab does not accept a dot at the start of project name. And also the tool we are using for synchronization (Git Mirror) does not allow to exclude a repository from an organization synchronization.

So I was wondering if renaming this project (.github) to use a name that would fit GitLab requirement would be doable? Thanks.

Invalid credential error at LDAP authentication cause of case sensitive comparison of database contact_ldap_dn and LDAP contact info

Module version

centreon.noarch 19.04.20-4.el7.centos (after checking the concerned file it doesn't seem fix on the last version neither)

Operating System

CentOS 7

Browser used

Google Chrome
Firefox
Internet Explorer IE11
Safari

Version: 111.0.5563.148

Additional environment details (AWS, VirtualBox, physical, etc.):
Virtual machine

Description

At LDAP authentication users may have "invalid credentials" error when the case of the contact_ldap_dn from LDAP is different from the Centreon database one.
On LDAP side this information is case insensitive so it can change at a LDAP configuration, migration or other maintenance step and it is causing authentication problem even if the user is the correct one.

Steps to Reproduce

To reproduce the issue :
--Log out from Centreon
--Change the user DN case on Centreon database table "contact", field "contact_ldap_dn"
Ex: Change CN=TEST,OU=FR,OU=TEST,o=test,C=FR to CN=TEST,OU=FR,OU=TEST,O=TEST,C=FR
--Try to login again > you should got "invalid credential" error

Describe the received result

"invalid credential" error

Describe the expected result

Be able to login

Logs

PHP error logs

"[17-Apr-2023 17:03:14 Europe/Paris] PHP Notice: Undefined index: ldap_auto_sync in /usr/share/centreon/www/class/centreonLDAP.class.php on line 962"


### Additional relevant information (e.g. frequency, ...)

This bug can be fix by adding function strtolower to make the comparison case insensitive on the /www/class/centreonAuth.LDAP.class.php 
--line 117 for 19.04 version:
$this->ldap->findUserDn($this->contactInfos['contact_alias']) !== $this->contactInfos['contact_ldap_dn'] replaced by strtolower($this->ldap->findUserDn($this->contactInfos['contact_alias'])) !== strtolower($this->contactInfos['contact_ldap_dn'])
--line 116 On the master branch:
$userDn !== $this->contactInfos['contact_ldap_dn'] replaced by strtolower($userDn) !== strtolower($this->contactInfos['contact_ldap_dn'])