Installation guide

• During installation, BlueDragon now prompts you to provide the option of
changing the default setting of restricting access to the localhost. You can provide
additional IP addresses or a range in the installation dialogue
• If you’re able to access the administration console and want to modify it to allow
other IP addresses to access it, note that the "License & Security" link (under
"General") has a field called "Allowed IP addresses".
• If you can't access the administration console, you can instead modify the
bluedragon-server.properties file in the config directory where BlueDragon is
installed. It has an entry of the same name.
In either case (whether designating the addresses in the installation dialogue, using the
administration console, or editing the XML file), the value is set by default to 127.0.0.1.
It accepts a comma separated list of IP addresses or ranges using the "*" wildcard (e.g.
192.168.1.*). Again, just be careful about opening it up too broadly. The whole point of
restricting it is reduced exposure of the administration console. Once you change it, be
sure to restart BlueDragon.
Of course, changing this may be useful for more than just accessing the administration
console, if indeed you chose not to implement web server integration and want to allow
others to get into your applications (in addition to the Admin). Just be aware of the
security implications when opening it to IPs on more than just your own internal network.
Indeed, a couple more points to keep in mind:
• If you're just wanting to open the web server to access the administration console
from machines other than that on which it's installed but within your own
network, you may want to also set your firewall to block access to the
BlueDragon built-in web server port (8080 by default) from outside of your
network.
• The admin password will be passed in clear text from your browser to the server.
Unfortunately, BlueDragon doesn't currently support SSL in its built-in web
server.
For now, if you're concerned about security, a better approach is to use SSH or other
approaches to tunnel into the machine.
6.2.2 Enabling SSH Tunneling
Another, more secure, way of opening remote access to the built-in web server (and
administration console) is to use SSH tunneling. This is easiest to do with a Linux/Unix
servers and any client, but it's also possible with a Windows server. Free SSH servers are
BlueDragon 6.1 Installation Guide
20