By Use Case
Binding a HTTPS certificate to your CurrentWare Server will allow your administrators to securely access the CurrentWare Web Console using HTTPS protocol.
For your convenience, the installer comes pre-shipped with a CurrentWare SSL certificate called console.currentware.app. It is installed during the cwServer installation. Follow the steps below to configure this SSL certificate on your cwServer.
Due to certain security restrictions with Firefox and Microsoft Edge, this guide is only compatible with Google Chrome.
*NOTE: The original HTTP (not HTTPS) entries are holding on to port 8997 and 8998. You cannot overwrite it with the new HTTPS binding. You must delete the HTTP entries first before you add the new HTTPS bindings. It is not recommended to have multiple bindings.
To get the CurrentWare Web Console to use the HTTPS certificate, you will need to update the app-config.json to point to the new domain.
On the cwServer computer, browse to C:\Program Files (x86)\CurrentWare\cwWebConsole\WebConsole\. Open the app-config.JSON file in notepad.
Update the app-config file to include the SSL certificate of the CurrentWare Web Console.
Update the app-config file to include the public IP address of your CurrentWare Web Console.
User accessing the Web Console from outside your LAN will see the "Not Secured" icon on their browser's address bar.
After the currentware.app certificate is configured successfully onto your cwServer, you will need to configure your computer or router to map the CurrentWare Web Console domain to your public IP address.
There are two ways to to this:
Note: Users accessing the web console from outside the network will encounter a security warning from Chrome (“Not Secured”). They must also update the host file on their computers to get past the login.
Use the hosts file to map the currentware.app domain to your server’s IP address. When you type in currentware.app on your computer, it will automatically point to the IP address of your CurrentWare Server.
You will need to modify the hosts file on all of your IT administrator’s computers.
Public IP address or LAN IP address* console.currentware.app
*Use a public IP address if you are accessing the web console from outside the network. Use an internal IP address if you are accessing the web console from your LAN only.
You will need to update the host file on every console computer outside your LAN in order to access the web console using this method.
Instead of editing the hosts file on your computers, you can opt to modify the DNS settings on your router. By doing this, you are asking your router to resolve the domain, currentware.app, to the IP address of your CurrentWare Server. This can be done by visiting your router configuration page.
Every router configuration is different. Follow your router’s user guide to find out how to modify the DNS settings.
Now you’re ready to launch web console with the newly binded HTTPS protocol. Open your favorite web browser and type in the following URL:
The existing CurrentWare Console shortcut on your desktop will become invalid. Right click on it and select Properties. Under the Shortcut tab, modify the Target to point to this location:
"C:\Program Files\Google\Chrome\Application\chrome.exe" https://console.currentware.app:8998/
Related KB article: Updating the console.currentware.app certificate for securing your CurrentWare Web Console