Views:

Behavior:
When adding an endpoint within the Identity Service or the Platform API, you encounter the following error.

<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>Microsoft-Azure-Application-Gateway/v2</center>
</body>
</html>

Solution:
If the User-Agent header is missing, the 403 Forbidden error will occur. To resolve this issue, the User-Agent header must to be added to the request. Below is an example of how this can be achieved.

POST {{idsaddress}}/connect/token HTTP/1.1
Host: login-emea.docuware.cloud

Accept: application/json
Content-Type: application/x-www-form-urlencoded
Content-Length: 196
User-Agent: {{applicationName}}/{{applicationVersion}}

grant_type=password&scope=docuware.platform&client_id=docuware.platform.net.client
&username={{username}}&password={{password}}&organization=Peters%20Engineering

The header typically consists of the name and version of the calling application, and should be sent with every request against the Identity Service and the Platform API. It is recomended to set the User-Agent as a default HTTP header in the HTTP client used.

KBA applicable to both Cloud and On-premise Organizations.

This article is valid for DocuWare versions: 7.11, 7.12, 7.13, 7.14, Rest API, 403 Forbidden, Identity Service, User Agent, HTTP, HTTP Header