When using HansaWorld REST API 2.0 a user authentication mechanism OAuth is used. This article describes what is the order of actions and setup steps to authenticate a user (Standard ID) with HansaWorld to get data from a Standard ERP server to flex.bi server.
The initial setup of REST API 2.0 is described in HansaWorld REST API 2.0 import page. Please follow steps there carefully as each of the requirements - HTTPs support for Standard ERP server, correct URL including the port used, accessibility from the internet, correct Client ID and Client Secret - is very important and can break the authentication flow.
There are three parties involved in each OAuth authentication process - the flex.bi server requesting data, StandardID server authenticating the user (StandardID) and the Standard ERP server serving the data. The image below has a separate column for each of these servers and the respective actions.
If the supplied Standard ID and password is not correct you will receive an error on the StandardID server (without redirect to flex.bi):
Access type must be 'offline' and response type must be 'code' |
If the supplied Client ID, Client Secret or redirect URL are not correct you might get various error messages such as:
Source application did not authorize your request |
If the supplied StandardID user and password were correct, but did not have access to the REST API or the specific register you will receive errors such as:
Source application did not authorize your request. Please check your authentication information. |
or
Received HTTP 405 error when requesting |
Related articles
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|