itgenoda191 Toegang tot de OAuth-gegevensbron vereist een geldig access token. Het access token kon niet worden verkregen. The client secret was incorrect.

When opening an Exact Online database in the SQL Editor I get:

itgenoda191
Toegang tot de OAuth-gegevensbron vereist een geldig access token. Het access token kon niet worden verkregen. The client secret was incorrect.
Als de client heeft geprobeerd te authenticeren via het veld ‘Authorization’-verzoekheader, MOET de autorisatieserver reageren met een HTTP 401 (Unauthorized) statuscode en het veld ‘WWW-Authenticate’-antwoordheader bevatten dat overeenkomt met het authenticatieschema dat door de client wordt gebruikt.

How do I fix this?

The error message is confusing; the client secret was not the cause of the problem. The Invantive Cloud merges up the actual text associated with itgenoda191 into the longer text.

The actual problem on itgenoda191 is:

itgenoda191
The client secret was incorrect.
Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). The authorization server MAY return an HTTP 401 (Unauthorized) status code to indicate which HTTP authentication schemes are supported.
If the client attempted to authenticate via the ‘Authorization’ request header field, the authorization server MUST respond with an HTTP 401 (Unauthorized) status code and include the ‘WWW-Authenticate’ response header field matching the authentication scheme used by the client.

Please check the client ID and client secret used. The should be the same as displayed on the Exact Online Apps Center and from the same country.

Please check the steps on Registratie Exact Online app voor gebruik met Invantive Cloud (Dutch).

In this case, the text “The client secret was incorrect.” indicates that probably the client secret was not correctly provided. Please remove the data container and register it again using the client secret.

Note that on November 17 a release was deployed that fixes some issues with registration of confidential information such as client secret.

It initially worked after refreshing authorizations, but after 10 minutes the same error faced again. Client ID and client secret were checked.