3.1.3 Configure repcli for Remote Access

The repcli tool can be used as standalone application to manage remote Repstance Server through the HTTPS protocol. 

The tool can be found in the following directories, once the product is installed:

• /opt/repstance/cli/macos – For MacOS Operating System
• /opt/repstance/cli/win – For Windows
• /opt/repstance/cli/linux – For Linux

Or they can be downloaded from here: 

• https://repstance.com/download/cli/macos/repcli.zip
• https://repstance.com/download/cli/win/repcli.zip
• https://repstance.com/download/cli/linux/repcli.zip

These remote clients are only able to connect using the HTTPS protocol and are supplied with the following default configuration: 

• HTTPS port is 8797
• For HTTPS initial use a Self-Signed Certificate is provided
• HTTPS authorisation “Token” in the form of the Repstance AWS Instance ID

In order to use the repcli utility to communicate with the remote Repstance Server it has to be configured using the repcli command “configure”.

The following example demonstrates the command syntax: 

Note – The verifyhttps parameter should be set to 0 to avoid the Self-signed certificate error. 

As the product is initially supplied with a Self-Signed Certificate it is highly recommended that the user replaces this with a security certificate of the required Security level themselves. The new certificate and key needs to be supplied to the Repstance Server and the appropriate entries in the /opt/repstance/conf/repstance.conf file need to be edited to reflect these changes: 

• key – path to the key
• crt – path to the certificate

Using this method, the default HTTPS port can also be changed by modifying the port parameter. 

The default token used to access the server can also be changed by modifying the token parameter in the same file. 

If the user wishes to prevent any external access, the port parameter should be set to value 0.