ramadda changes

[Jeff McWhirter]

Hi RAMADDA users,

I wanted to send an update on some recent changes to some RAMADDA configuration options.

RAMADDA can run behind a  proxy server (e.g. Apache) on a given set of custom HTTP and HTTPS ports. Because RAMADDA generates absolute URLs that need to point to the external proxy server ports and hostname, there was a configuration option through the Admin->Settings interface.

Likewise, there was a setting to force all connections to be done through HTTPS.

I made a change to the configuration to not have any network/server configuration be done through the web interface. This prevents the possibility of locking out access to your RAMADDA if something is mis-configured.

These configuration options are now set in an external .properties file in your RAMADDA home directory. If you had these set through your Admin interface you will need to  reconfigure your settings and add them to a properties file. Here is the documentation-

https://ramadda.org/repository/userguide/installing.html#external_ports

Also - I made another change to limit the SSL ciphers that can be used for HTTPS to a more restricted list. This tightens up the security of HTTPS connections. If you see any problems with the new release please contact me.

I have made a new release with these changes-

https://ramadda.org/release

-Jeff