Encrypt every new/edited property: bug or feature?

Personally, I think it’s a bug.
Affects: Openfire 3.9.2/3.9.3.

I noticed the editing a property value via the Openfire admin interface leads to encrypting the value. For the test purpose I’ve created the new property - the same result. At the System Properties page it is displayed as ‘hidden’, in database - encrypted, security.xml contains the new property name for encryption.

Yes, this is definitely a bug - thanks for the detailed report. Filed as OF-800; expect to be resolved shortly.

This still happens.

I’m trying to integrate openfire with a custom mysql database.

After editing openfire.xml and restart openfire, while accessing web admin console this error log is showned:


Problem accessing /setup/setup-host-settings.jsp. Reason:

Server Error

Caused by:


at org.jivesoftware.util.JiveGlobals.setupPropertyEncryptionAlgorithm(JiveGlobals. java:867)

Any clue or workaround to solve this problem?


This will be fixed for 3.10.0 version (https://igniterealtime.org/issues/browse/OF-800). You can use 3.10.0 Beta for now, or the latest build, which is closer to the final 3.10.0 version (http://bamboo.igniterealtime.org/artifact/OPENFIRE-NIGHTLYWINDOWS/shared/build-1 606/Project-Windows-distribution-files/o… ). After you install it, you should recreate encrypted system properties.