You can install the iManage Drive Port Forwarding Service to enable support for web extensions with iManage Drive on Microsoft Windows Server devices, which use multiple iManage Drive users. This allows iManage Drive to use web extensions that call the iManage Drive local REST service and need a fixed port to work. It also helps if you're using multiple instances of iManage Drive on the same device.
NOTE: Support for iManage Drive Port Forwarding Service is available only on Microsoft Windows Server devices, which use multiple iManage Drive users.
To configure the port:
Download the iManagePortForwardingService installer from iManage Help Center.
Run and install the installer on your device.
Browse to C:\ProgramData\iManage\DrivePortForward\ .
Create a port.txt file and add the port number in the file.
If no file is added in the location, then the default value iManage Drive uses is 8010.Set enable_local_rest_service_port_forwarding setting in the admin_setting.yaml file to true.
After the port forwarding services are enabled, the iManage Drive Port Forwarding Services service:
Listens for requests on a fixed port that is configured.
Supports a port registration rest api of the format: /drive/register_local_port?port=<local_service_port> where local_service_port is port number configured.
Additionally, when the iManage Drive Port Forwarding Services service receives a request on the static port, it does the following:
Ignores any requests that aren't from a local ip address such as 127.0.0.1 or localhost.
Gets the process information of the process that owns the request port.
Gets the username of the process that owns the request port.
Looks up the iManage Drive service port that is registered for the username of the process that owns the request port.
Forwards the request to the registered service port.
The iManage Drive Port Forwarding Services service uses:
Uses the request port to lookup the username of the request
Uses the registration request port to determine the username of the registration request
Uses the registration request port to determine which process is being registered
iManage Drive continues to validate the token, so the Manage Drive Port Forwarding Services service shouldn't need to validate any tokens.