3160656 - Why do we receive the status code 500 in our Sharepoint Online?

We have a problem with authentication in our Signavio workplace. We are using AzureAD via Office 365 to authenticate users. When a user tries to navigate to the Signavio Collaboration Hub via our intranet, the following error message is displayed:

Could not authenticate towards Signavio

Details: getting handover from request /intra/authhandover failed. Status code: 500.

Do you have any idea on what we should do to fix this?

There are several potential causes for this error message. In order to find the appropriate solution, please open the developer console of your browser (F12) and open the tab "Network" or "Network analysis". Then please reproduce the issue.

Within the Network analysis search for the request "/intra/authhandover". It should display the Status code 500. Now please click on this request entry and search for the 40x error message in the advanced view. Now depending on the actual error message displayed please follow the appropriate steps:

400 Azure AD access token request returned

This error message means that currently no connection between your Azure AD and our Signavio system can be established. The underlying cause here is that incorrect IDs have been provided for the authentication in the Signavio Explorer. Please compare the IDs in "Setup" → "Manage Collaboration Hub Authentication" with those generated in according to this page.

401 Azure AD accessdata:image/jpeg;base64, credentials for the connection towards Azure Active Directory.

Please perform the steps that are described on this page.

---

403

This message confirms that validation of the IDs (the green check mark in the "Collaboration Hub Authentication" panel) have been successful, but the user either has been deleted or has lost pdata:image/jpeg;base64,/span>

Please create a new Azure AD account for the Signavio system according to the instructions here. Afterwards, please update the IDs in the authentication pane, and download and install the app again. Please note that the current app also needs to be removed from the recycle bin (see also here).