GLPI Webhook Mediatype not working

[Carlos_Castillo]

Hi Everyone!

I have a problem with the GLPI webhook media type, I just enabled and set the webhook but is not working, is not creating problems in my GLPI. I'm currently using Zabbix 6.4.13 and GLPI 10.0.12 and the webhook is this: https://www.zabbix.com/la/integrations/glpi.

This is what I see when I try to test the webhook:





This is the log:

[B]Media type test log[/B]
00:00:00.116 [Debug] [ GLPi Webhook ] Sending request: http://172.16.18.68/apirest.php/Problem/ {"input":{"name":"{ALERT.SUBJECT}","content":"{ALE RT.MESSAGE}\n<a href=http://172.16.5.10/tr_events.php?triggerid={TRIGGER.ID}&eventid={EVEN T.ID}>Link to problem in Zabbix</a>","status":1,"urgency":"{EVENT.NSEVERITY}"}}
00:00:00.189 [Debug] [ GLPi Webhook ] Received response with status code 200
00:00:00.189 [Debug] [ GLPi Webhook ] Failed to parse response received from GLPi
00:00:00.189 [Debug] [ GLPi Webhook ] ERROR: Failed to process response received from GLPi. Check debug log for more information.

[Carlos_Castillo]

Here is the webhook configuration:

[Carlos_Castillo]

and this is the _log in the GLPI server:


One important stuff to mention is that I'm not seeing any requests for today, is like Zabbix is not reaching GLPI side

[Carlos_Castillo]

I made an update in Home / Setup / General / API Clients and set the Log Connections to "Logs" and after that I'm able to see the API calls in the logs

[Carlos_Castillo]

I found the issue after checking the GLPI php-errors.log file:

[2024-04-15 15:01:31] glpiphplog.CRITICAL:   *** Uncaught Exception TypeError: Unsupported operand types: int << string in /var/www/html/glpi/src/CommonITILObject.php at line 2583
  Backtrace :
  src/Problem.php:298                                CommonITILObject->prepareInputForAdd()
  src/CommonDBTM.php:1297                            Problem->prepareInputForAdd()
  src/Api/API.php:1856                               CommonDBTM->add()
  src/Api/APIRest.php:317                            Glpi\Api\API->createItems()
  apirest.php:57                                     Glpi\Api\APIRest->call()
  public/index.php:82                                require()
zz0.c5goe3sddb7zz

The severity can't be a string, it must be an int

[cyber]

But your media type parameters contain severity as number.. {EVENT.NSEVERITY} So where the string comes from ?

[davbaq]

Hello, I have the same problem, my version of GLPI is 10.0.15 and zabbix is 7.0. When I see the GLPI logs, the error is as follows


When validating the line that mentions this is what it indicates

if (
!isset($input["urgency"])
|| !($CFG_GLPI['urgency_mask'] & (1 << $input["urgency"]))

The error appears to be related to the "urgency" variable being passed as a string instead of an integer but I don't know how to solve it

[axis360]

Did anyone has some progress on the said matter?
i am stuck too at this error.
Anyone found any solution?

[davbaq]

Validating error indicates that there is a problem with data type manipulation in the GLPI code. Specifically, you are trying to use the bit shift operator (<<) with a text string, which is not supported.

Solution

Take backup of the CommonITILObject.php file

Review the Code: Open the file mentioned in the error (/GLPI path /glpi/src/CommonITILObject.php) on line 2583 and review the code that causes the error.

Adjust the Data Type: Make sure that the variables involved in the operation are of the correct type. For example, if an integer is expected, convert the string to an integer before performing the operation.

Valor original


if (
!isset($input["urgency"])
|| !($CFG_GLPI['urgency_mask'] & (1 << $input["urgency"]))
) {
$input["urgency"] = 3;
}


Add(int) like this;



if (
!isset($input["urgency"])
|| !($CFG_GLPI['urgency_mask'] & (1 << (int)$input["urgency"]))
) {

Save and restart the web server service

With that it already worked for me





What Did the Original Line Do?

1. Existence check: !isset($input["urgency"]) checks if the urgency value is not present in the $input array.
2. Validity check: !($CFG_GLPI['urgency_mask'] & (1 << $input["urgency"])) checks if the urgency value is valid based on the configured urgency mask ($CFG_GLPI['urgency_mask']) . The 1 << $input["urgency"] operation shifts bit 1 to the left by the urgency value, creating a specific bit mask for that value, and then performs a bitwise AND operation with the configured urgency mask .

Solution

The error occurred because $input["urgency"] was not always an integer. The solution involves forcing the conversion of $input["urgency"] to integer before using the bit shift operator. This ensures that the operation succeeds and prevents the type error.

Explicitly converting $input["urgency"] to integer ((int)$input["urgency"]) ensures that the bit shift operation executes correctly, eliminating the type error and allowing urgency checking works as expected. This modification is crucial to maintain the robustness of the code when handling different types of data input.

[markosa]

Carlos_Castillo in your first post, there can be seen that media type sends data (event.nseverity) as string, "urgency":"{EVENT.NSEVERITY}"} as we can see that macro {EVENT.NSEVERITY} is placed within double quotes. I would fix GLPi media type script which creates post request instead of changing GLPi php.

[davbaq]

If you are right, by adjusting the .yaml file as follows, I was able to leave the glpi php file unchanged

Original

data = {
'input': {
'name': params.alert_subject,
'content': params.alert_message + '\n<a href=' + GLPi.getProblemUrl(params.zabbix_url, params.trigger_id, params.event_id, params.event_source) + '>Link to problem in Zabbix</a>',
'status': 1, // Set status "New"
'urgency': params.event_nseverity
}
};
response = GLPi.request('post', glpi.url + 'apirest.php/Problem/', data);

tight

data = {
'input': {
'name': params.alert_subject,
'content': params.alert_message + '\n<a href=' + GLPi.getProblemUrl(params.zabbix_url, params.trigger_id, params.event_id, params.event_source) + '>Link to incident in Zabbix</a>',
'status': 1, // Set status "New"
'urgency': parseInt(params.event_nseverity) // Convert urgency to integer
}
};
response = GLPi.request('post', glpi.url + 'apirest.php/Problem/', data);

[renatobeiriz]

davbaq i triyed bur the problem persist

[steven b]

bonjour á tous !
je rencontre aussi un problème toujours le type media Glpi sur ZABBIX en se moment je suis a la version 7.0.4 de ZABBIX et 10.0.6 de GLPI lorsque je configure une erreur persiste et me parle beuacoup de l'app_token manquant. ce pendant j'ai beau activer l'API restfull de GLPI , creer un client API, generer l'le jeton API d'un utilisateur GLPI le copier le coller sur le parametre glpi_token preciser les urls l'erreur reste inchanger j'ai fait des recherches mais je suis un novice dans le domaine de la programmation et pour les API je souhaite que vous eclairez ma lanterne comment devrai-je m'y prends pour que l'utilisateur GLPI que j'ai creer puisse recevoir des notification venant de zabbix. Dans le pieces jointes

[leonardon]

Hi, were you able to resolve this issue? I'm having the same problem.

[CLem8667]

Bonjour,
J'ai le même problème, avez vous trouvez une solution depuis votre post ?

[osmoonlight]

I am having also problems with getting this to work. I just started using the ticketing function in GLPI and I would like Zabbix to create its own tickets. I followed the set-up information from the official template (Source of README.md - Zabbix - ZABBIX GIT), but I am stumbling at the last hurdle it seems.

Zabbix 7.4 on a Ubuntu server, GLPI 11 as docker container

In GLPI, enabled legacy REST API and created a API client:



I did not create the app_token, thus did not change the script on the Zabbix side.
Created a user, gave super-admin rights (just in case, to test) and created a API token. The token works, more below...

In Zabbix, imported the template, added the necessary information

The glpi_user_token is a left over from testing, but shouldn't make a difference

Created a Zabbix user with the GLPI media attached and attached super admin rights for testing.

Ran the two scripts from Zabbix:

curl -X POST http://10.10.11.30:8769/apirest.php/initSession -H "Content-Type: application/json" -d "{"user_token":"[redacted]"}"

and

sudo curl -X POST http://10.10.11.30:8769/apirest.php/Ticket -H "Content-Type: application/json" -H "Session-Token: [redacted]" -d '{
"input": {
"name": "Zabbix Alert: Disk Space Low",
"content": "Host: server01\nProblem: Disk usage over 90%\nSeverity: High",
"status": 1,
"urgency": 4,
"requester": 10
}
}'
and received the test ticket in GLPI.

Okay, should work. However, when a problem pops up in Zabbix, I get the ominous "Unknown INFO" error.

Grateful if somebody could point out my error(s) and make me a happy system admin again.