Some background... with the --addduipreferences parameter, that is just for version OX6, so that will not won't work here for this situation. Also, this has not been extensively tested, so we would suggest you test this out first in your Staging or QA env. Note to be sure your spacing is correct in yml files. If not, your OXAppSuite will not start! In your /opt/open-xchange/etc/meta/guard.yml, add the following
| Code Block |
|---|
| language | yml |
|---|
| title | /opt/open-xchange/etc/meta/guard.yml |
|---|
| com.openexchange.guard.defaultEncrypted:
preferencePath: oxguard//defaultEncrypted |
This line essentially maps a middleware configuration value to the UI value.
IMPORTANT  You would then need to add a default value for this in a properties file (probably the guard-api.properties, but could be in any configuration file in the middleware).
If you are running Guard on the middleware servers (not separate servers), you could also put this in the guard-core.properties file. | Code Block |
|---|
| title | /opt/open-xchange/etc/guard-core.properties |
|---|
| com.openexchange.guard.defaultEncrypted=false |
If the middleware doesn't have a default value for this setting, then Guard will think that there is a need for upgrading from 2.8 to 2.10 (when this value was added),
and the users would or will lose their default settings for signing, encrypt, and inline. Finally, the moment you you've been waiting for. How to set the default for composing an email to be encrypted.
Command would be | Code Block |
|---|
/opt/open-xchange/sbin/changeuser -A oxadmin -P secret -c 1 -i 5 --config/com.openexchange.guard.defaultEncrypted=true |
-A = the oxadmin user, -P = the oxadmin password, -c = the context, -i = the user ID
This can also be set at context level if your have a large context of users. This will set the value to true for the user, but they will be able to uncheck it if they choose. |