Issues with REST BAQ

Experts' Corner
41

For everyone Information, this issue has been solved

42

Yes, this ‘works around’ the issue. The problem is those customers an SaaS can’t make changes to the web.config so they are out of luck.

Another SaaS buyer beware issue

1 Like
43

Note : OData v4 is supported by MS ExcelÂŽ 2016 or higher.
Important : To be able to get data from a Service/BAQ feed into Excel using REST API v.2, you must:

  1. exclude the api-key parameter from your requests, and
  2. disable the default API Key requirement for REST requests by setting the value of the

EnforceApiKeyForRestApiV2 tag in the appSettings section of the system configuration file to false.

44

Turning off security is not really a good work around though. It makes your system just as vulnerable as running unencrypted ODBC. No supplier (Phocus included) should be using unencrypted ODBC, which is the default. To enable encryption see Using Always Encrypted - ODBC Driver for SQL Server | Microsoft Learn.

Also, using a single username and password is generally a poor security practice, so enable Azure Active Directory and use a Secrets manager like Azure Key Vault or HashiCorp’s Secrets Engine.

ODBC users beware. Most of you are sending data in the clear, maybe even your username and password.

1 Like