Sometimes a Fileserver or a Network-attached storage (NAS) is not configured correctly when serving PDF Files and are using a wrong HTTP Header like "Content-Type: text/html". This Content-Type has to be set to application/pdf. You can check out the Content-Type used with Web Development Tools that are included in most Browsers today. Open the full path in your Browser and check the HTTP Headers in the "Network" Tab.

You can save the Network Share using the Administration > File Management Menu in Durst Workflow. There you can create, edit and manage Shares and Folders. The Rest-API is then using the saved credentials.

Do not use #, & or ? for username and password, because these are needed characters in the url query string. Ampersand (&) is used as a seperator, the question mark (?) to pass the query string and the hash (#) to further specify a subsection.

Check the Response Code of the Login Request. Successful Logins result in 200 OK – unsuccessful Login attempts result in 401 Unauthorized

Please check, if you are using the full base path for Rest-API requests: http://xxx.xxx.xxx.xxx:8081/pms/

This is of course possible. The prerequisite for this is in the simplest case the use of a static IP or a host name and a corresponding port forwarding to the internal workflow server on port 8081.

From the network point of view, configurations as follows are possible. The external port number can be arbitrary apart from the frequently used standard ports. Some examples:

workflow.domain.com:8081 → 127.x.x.x:8081
workflow.domain.com:52211 → 127.x.x.x:8081
11.47.87.112:8081 → 127.x.x.x:8081

For security reasons, we recommend that you allow dedicated access from the outside using whitelisting. This means that access to Workflow is blocked by default, the source addresses of Smart Shop or LiftERP are whitelisted individually.

In case of a connection e.g. of an online store to Durst Workflow, it must also be guaranteed that Durst Workflow itself has access to the sources to pull print data from the web/file server (http/https/smb).

The IT service provider is also free to use other methods for securing, e.g. a reverse proxy. Basically, it is only necessary to ensure that Durst Workflow can be reached at destination port 8081.