Some test text!
This guide details how you can improve the overall security of WebViewer Server in your environemt.
In order to secure your container in your environment, we suggest you do the following.
For more in depth and general purpose solutions to improving container security, please refer to this guide.
In addition to the to the innate security advantages of containerization, we have taken additional measures for this specific container:
WebViewer Server is designed to request files from a server. This means that between all clients and the file server, WebViewer Server can expose access to all files on the file server. The common way of dealing with this is to add security to your server. This can be done by:
If you are concerned with clients still having access to files which they have lost access to we recommend enabling the TRN_FORCE_URL_RECHECK . This will force the file links to be rechecked for validity every time they are requested.
We recommend reviewing our security configuration options here to improve web security. We recommend the following options be set within your system.
Set this to false to prevent vulnerabilities arising from the demo code packaged with WebViewer Server
Set this to your Webviewer client domain to restrict requests to that domain.
Set this to the root of your file server, which will restrict file requests to any other domain.
If you have concerns with cached files being accessible if the link is given out, you can set the following options. Keep in mind these options will come with a loss in performance due to the loss of cache sharing.
Get the answers you need: Support