Skip to main content

    Filter by idea status

    Filter by product

    629 Ideas

    Make centreon compatible with linux centrify users - For UpgradesIn Backlog

    Hi all,We use here Redhat 8.10.Our policy is not to create local users on our linux systems.Instead all our users are in Active Directory (with linux attributes).We use Centrify to map the Ad users to the local linux system (https://delinea.com/centrify)This is why all our centron users are not present in /etc/passwd (centreon, centreon-broker, centreon-engine, centreon-gorgone)But they do exists and can be used as usual to start process, as owner of files ...etc → All our Centreon Platform is running well with this Centrify configuration ….BUT we are facing an issue while upgrading :EX:  during  “dnf upgrade centreon-common.noarch”The rpm scriplet provided by centreon runs this : if getent passwd centreon-broker > /dev/null 2>&1; then  usermod -a -G centreon-broker centreon  usermod -a -G centreon centreon-brokerfiBut it fails with : Running scriptlet: centreon-common-23.10.11-1.el8.noarch 7/138usermod: user 'centreon' does not exist usermod: user 'centreon-broker' does not exist usermod: user 'centreon' does not exist usermod: user 'centreon-engine' does not exist error: %prein(centreon-common-23.10.11-1.el8.noarch) scriptlet failed, exit status 6This is because ‘usermod’ need real linux local users (present in /etc/password)So the package is not installed … and other foloowing commands (chown /  chmod) in the scriptlet are not executed at all….Would it be possible not to exit when these ‘usermod’ are failing ??This could be possible with the || true option for the usermod commands :usermod -a -G centreon-broker centreon || true Thanks 

    Lenteur d'affichage des downtimes - index manquant - LIKE '%%'Released

    Bonjour,En prestation pour un client grand compte, je constate des lenteurs d’afficage lors de l'appel à la page downtimes  /centreon/main.php?p=21001il se passe une bonne quinzaine de secondes, au  minimum, avant que les données apparaissent.En recoupant avec un Expert DBA de mon client grand compte, il s'avère que la requête SQL de l'affichage des downtime ne semble pas optimale. La partie des filtres, notamment, ne sont pas correctement indexés (host, acteur, descriptions...)De même, si les champs de recherche sont vides, il n'est pas nécessaire de mettre LIKE '%%'. la requete en question : (SELECT SQL_CALC_FOUND_ROWS DISTINCT 1 AS REALTIME, d.internal_id as internal_downtime_id, d.entry_time, duration,        d.author as author_name, d.comment_data, d.fixed as is_fixed, d.start_time as scheduled_start_time,        d.end_time as scheduled_end_time, d.started as was_started, d.host_id, d.service_id, h.name as host_name,        s.description as service_description  FROM downtimes d, services s, hosts h WHERE d.host_id = s.host_id AND d.service_id = s.service_id AND s.host_id = h.host_id AND d.type = 1  AND d.cancelled = 0 AND s.description LIKE '%%' AND h.name LIKE '%%' AND d.comment_data LIKE '%%' AND d.end_time > '1732196593'  AND d.comment_data NOT LIKE '%Downtime cycle%'  AND d.author LIKE '%%') UNION (SELECT DISTINCT 1 AS REALTIME, d.internal_id as internal_downtime_id, d.entry_time, duration,  d.author as author_name, d.comment_data, d.fixed as is_fixed, d.start_time as scheduled_start_time,  d.end_time as scheduled_end_time, d.started as was_started, d.host_id, d.service_id, h.name as host_name,   '' as service_description FROM downtimes d, hosts h  WHERE d.host_id = h.host_id AND d.type = 2  AND d.cancelled = 0 AND h.name LIKE '%%' AND d.comment_data LIKE '%%' AND d.end_time > '1732196593'  AND d.comment_data NOT LIKE '%Downtime cycle%'  AND d.author LIKE '%%') ORDER BY scheduled_start_time DESC LIMIT 0, 50Pourriez-vous prendre en compte ces remarques pour vos futurs releases ?Cordialement Emanuel BourelADN-Consultingticket de support associé : https://support.centreon.com/hc/fr/requests/79841

    hboulouzSteward *

    Add .pfx format support in the X.509 certificate pluginNeeds Votes

    Hello everyone, o7I would like to suggest an enhancement for the X.509 certificate monitoring plugin.Currently, the plugin supports checking certificates in PEM format but does not seem to directly handle .pfx (PKCS#12) files, which are widely used for securely storing certificates and private keys.Adding support for the .pfx format would simplify certificate monitoring in many environments, especially where certificates and private keys are exported or deployed using this format. Is such an enhancement feasible? Or are there already existing solutions or workarounds for this?Thanks in advance for your feedback!FRENCH ================================================================== Bonjour à tous, o7Je souhaite proposer une amélioration pour le plugin de supervision des certificats X.509.Actuellement, ce plugin prend en charge la vérification des certificats au format PEM, mais il ne semble pas gérer directement les fichiers au format .pfx (PKCS#12), qui sont pourtant très courants pour le stockage sécurisé des certificats et clés privées.Ajouter le support du format .pfx permettrait de simplifier la supervision des certificats dans de nombreux environnements, notamment ceux où les certificats et leurs clés privées sont exportés ou déployés via ce format. Est-ce qu’une telle évolution est envisageable ? Ou existe-t-il déjà des solutions ou contournements à ce sujet ?Merci d’avance pour vos retours !