-
Improvement
-
Resolution: Unresolved
-
Major
-
1.8.0
-
None
-
4.10.1
-
Oui
It seems that GLPI do not accept anymore request parameters.
When fixing the issue ensure to stay compliant with GLPI olders version (by adding a parameter may be)
Errors raised when trying to retreive data :
Niveau : ERROR Catégorie : org.ametys.plugins.glpi.TicketGlpiManager URI de la requête : /generate/intranet/_plugins/link-directory/dynamic-information/update/intranet/default Message : An error occurred while contacting the GLPI Rest API (status code : 401). Response is : ["ERROR_SESSION_TOKEN_INVALID","session_token semble incorrect"] Emplacement : org.ametys.plugins.glpi.TicketGlpiManager._callWebServiceApi(TicketGlpiManager.java:423)
Niveau : DEBUG Catégorie : org.ametys.plugins.glpi.TicketGlpiManager URI de la requête : /generate/intranet/_plugins/link-directory/dynamic-information/update/intranet/default Message : GPLI identity not found for user UserIdentity [login=… population=utilisateurs] Emplacement : org.ametys.plugins.glpi.TicketGlpiManager.loadUserInfo(TicketGlpiManager.java:203)