When configuring connectivity between the Collaboration Server and the Library Server, manipulation of several configuration files may be required. For example, when attempting to configure HTTPS/TLS, the config.json needs to be modified (Documentation). After manual modifying these configuration files, it's possible that you may encounter some errors when trying to connect Collaboration Server to the Library Server.
In these situations, it is useful to review the Collaboration server logs, Library logs, Tomcat logs, and/or DSSErrors.log. One such error you may find in the Collaboration Server logs is “Unexpected token a in JSON at position.”
This error indicates a syntax error within the config.json file that exists in the CollaborationServer file directory. One possible source of a syntax error in the config.json file is improperly defined file paths. In order to properly define the path of a file in the config.json file, you must utilize two slashes rather than a single slash. This is because strings surrounded by double quotes allow many escape sequences that begin with backslashes.
Below is an example of a valid file path for on a server running on a Windows operating system:
"keystoreFile": "C:\\Program Files\\certs\\Example.p12"
Validate that the file paths specified within your config.json file are using the correct syntax. If that is not the source of the problem, check to make sure your config.json file has been saved in a valid format. This can be reviewed through the use of a third party json validator.
Available json validator:
https://jsonformatter.curiousconcept.com/
