Graph Connector suddenly stopped working / not able to retrieve token

0
We are using the MS Graph connector to export meetings to our shared outlook calendar. This has worked perfectly for us for the past months. All of a sudden, without any updates from our side, the working of this API stopped working. We checked the authentication within the Widget, and are not able to retrieve a token anymore. We have check the API itself by using Postman to replicate te problem. With Postman everything works fine. It seems like a sudden bug in the Widget, but we are running out of knowledge about this. Does anyone face the same problem? Problem now; When trying to create a new authentication in the Widget configuration back-end, we fill in the Tenant ID, Client ID and the secret. After that, the widget tries to retrieve the “Well-Known configuration”. At this point, we don’t get any communication from Azure and we are not getting the response we need.   Can anyone help us with this, things we can try to narrow down this problem perhaps?     Some of the log files from Mendix: 2022-06-02T11:26:38.238028 [APP/PROC/WEB/0]  ERROR - Microsoft Graph: POST Request failed: Connection refused (Connection refused) 2022-06-02T11:26:38.240161 [APP/PROC/WEB/0]  ERROR - Connector: An error has occurred while handling the request. [User 'z003mkcz' with session id '8309001c-XXXX-XXXX-XXXX-XXXXXXXXdc1c' and roles 'Administrator, SiemensUser'] 2022-06-02T11:26:38.240180 [APP/PROC/WEB/0]  ERROR - Connector: com.mendix.modules.microflowengine.MicroflowException: Variable should not be null
asked
1 answers
0

Hi Axel,

 

The problem to solve is “ Variable should not be null”. One of the “mandatory” fields is empty. Look into the variables using the debugger just before the call. Do you see all fields being populated as you expected? If so, maybe the specifications of the other end changed. Have a look at their documentation.

 

M.

answered