I’ve maganged to setup the connection to the Exact Online API from postman.
Now I try to setup the connection from the SF but we running into an invalid_request error as a result.
I’ve used the same input variables and keys, so at the moment I’ve not a clue why this result is happening:
Has anybody in the community succesfully connected to the Exact Online API.
Best answer by Dick van den Brink
View originalA new blog post is just released, maybe it provides some helpful extra information.
It is good to hear that everything is already working for you!
Regards,
Dick
Hi Erwin, thanks for all your support and tips but I don’t think it’s an authentication problem and I’m really getting stuck whatever I try. (Sorry for the layout but this f… editor suddenly creates a table when I copy the result from the proces montior)
I tried 3 methods, see below in the bold indicated sections.
So I’m totally getting stuck at this moment, really well knowing that all this API stuff is pretty new for me.
I’m getting a result from exact online, but the result is “invalid request”. If there is something with the authorization Exact will give back another message. I’m pretty sure I’m almost there, but I am not able to see what the SF creates as the final call. I can edit the connector params and I can test it. I can see the result in the proces flow monitor but I cannot see what the SF is finally sending to exact.
----------------------------- Refresh token via http connector failes in invalid request
When I try the refresh token via the http connector I’m getting back an header with this info:
| headers | [{"Key":"Content-Length","Value":"27"},{"Key":"Cache-Control","Value":"no-cache,no-store"},{"Key":"Content-Type","Value":"application/json"},{"Key":"Expires","Value":"-1"},{"Key":"Pragma","Value":"no-cache"},{"Key":"Referrer-Policy","Value":"strict-origin-when-cross-origin"},{"Key":"X-Content-Type-Options","Value":"nosniff"},{"Key":"X-Xss-Protection","Value":"1; mode=block"},{"Key":"Date","Value":"Tue, 23 Nov 2021 10:28:19 GMT"},{"Key":"Connection","Value":"close"},{"Key":"Set-Cookie","Value":"ExactOnlineClient=SB0Q8zFGGDK7ZWzICaPXt7XxiiRFGATAnZ1rZSQSjWEBmQTOiV0wPjHvp/WwU/6po8wy3y3w68xb09aHX3GnPOXQegom1fOso2L8nbALt6mxqP13wP8pXanYW4zTVqmKcHZwdg9gRM8dIiYjozg0GQSvyP7ChbMYEcV4BzrKgK0=; SameSite=lax; expires=Mon, 31-Dec-2198 23:00:00 GMT; path=/; secure; HttpOnly"},{"Key":"Strict-Transport-Security","Value":"max-age=31536000 ; includeSubDomains ; preload,max-age=31536000 ; includeSubDomains ; preload"}] And in the result parameter: invalid request. In de debug: The remote server returned an error: (400) Bad Request. So nothing about authorization or authentication. Exact is not able to understand the request we put. ----------------------------- Endpoint request fails in Unauthorized When I try the endpoint to get the accounts at this moment I’m running into Unauthorized. However I just retrieved a new access token via postman.
|
------------------- oAuth connector fails with an SF error message. No debug no result
I’ve setup an 0Auth step in my proces flow as well. I created an oauth server:
And I created a really simple workflow with only this 1 step.
The result in the end applicatoin. Step 2 which is the oauth step fails directly
Hello Edwin,
I do recommend using the OAuth connectors over the HTTP connector. Note that the purpose of the OAuth login connector is to obtain your initial access_token and, more importantly, your refresh_token. Once you have these, you can use the OAuth refresh token connector to exchange the refresh_token for a new access_token.
A few side notes here regarding Exact Online:
I'm not sure if you even want to use the OAuth login connector or if you want to jump straight in to the OAuth refresh token connector, because you already seem to have a refresh token. However, if you need to use the OAuth login connector, you will need to fix a few things which I have outlined below.
Once you have your refresh token, you will want to use the OAuth refresh token connector whenever you need to obtain a fresh access token after it has expired. The OAuth refresh token connector simply has one input parameter, the refresh token. It will output a new access token and a new refresh token. Note that your old refresh token is now invalid, only the new refresh token will work.
Now that you have your access token and a way to continuously refresh it when necessary, you can make your API calls by using an HTTP connector. Our Authentication type input parameter is missing the value ‘Bearer’ which you will need to use for your API calls, but you can add Bearer authentication yourself by setting the following header:
[{"Key":"Authorization","Value":"Bearer {access_token}"}]
Note Exact Online's documentation on this as well:
With all this said, you might still get that error in the Windows GUI, if so, please expand the error so we can see what is going wrong.
I hope this helps.
Vincent,
I changed the connector to the refresh connector. At least my Object Reference message is gone now.
Now I’m running into an -100 status_code which is as far as I can see not documented.
We’ve setup 2 applications in Exact online. 1 for postman and 1 for the TW application. In postman everything is working, and I’m now using the refresh token from postman in the SF. Of course I use the same client_id and the same secret_id as in postman. So all three parameters belong to the same connection. I think exact cannot ‘see’ where we’re calling from as long I don’t mix up the credentials.
What I’m doing now is:
1. An authorization request in postman. I’m doing that in a browser. Exact asks me to login including the two way authentication. Exact returns in the URL an in this URL is the Code for the first Code request
2. The next step is the first token request which I run in postman.
3. This step returns in json the acces token and the refresh token as below
{
"access_token": "gAAAAAmRzs…………..”,
"token_type": "bearer",
"expires_in": "600",
"refresh_token": "Y2MN!IAAAAL-IqLx………….."
}
So I use postman (till now) for the first refresh code.
I’ve setup step 4 (getting the refresh token) in the SF with the 0auth refresh token process flow action. In this action I use the exact online oauth server (with the corrected path as you said) and the only input is the refresh token.
I’ve copied the refresh token from postman in the process variable and I connect the process variable refresh-token to the input.
But still the result = -100. There is no other message or stack trace. Also there is nothing in the debugger.
In the Indicium log of the SF (I run the application against the SF) there is also nothing.
There is one message returning every 15 minutes, but I think that has nothing to do with the process I’m trying to setup now
2021-11-25T14:45:00.0089779+01:00 [ERR] Process action 'http_connector' was not provided a (valid) value for its 'URL' parameter. (0680995c)
Can it be a firewall issue?? Since I’m running it from the Windows GUI, there is no activity at all in Indicium. This IIS where the Indicium is running is not reachable from the Internet ‘yet’.
If I do a request, should this be visible im the Indicium logs? And maybe I can do a request to the outside world, perhaps the answer is simply not coming back because of a firewall rule / connection?
I did a setup in another installation where the indicium is ‘reachable’ from the internet there the refresh token action is working…..
Hello Edwin,
The -100 status code means that the process action is unsupported. The version of the Windows GUI that you’re using is too old, it does not support the OAuth process actions.
I hope this helps.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
