-
Type: Epic
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: nuxeoctl start/stop/admin
-
Tags:
-
Impact type:API change, Configuration Change
-
Upgrade notes:
-
Sprint:DevOps Sprint 10
Sensitive configuration data can be encrypted to avoid clear data in the configuration files, especially nuxeo.conf.
New commands usage:
nuxeoctl encrypt [--encrypt <algorithm>] [<clearValue>..] [-d [<categories>]|-q] Output encrypted value for <clearValue>. If <clearValue> is not provided, it is read from stdin. nuxeoctl decrypt '<cryptedValue>'.. [-d [<categories>]|-q] Output decrypted value for <cryptedValue>. The secret key is read from stdin. nuxeoctl config [--encrypt [<algorithm>]] [--set [<template>]] [<key> <value>].. <key> [<value>] [-d [<categories>]|-q] Set template or global parameters. If <value> is not provided and the --set 'option' is used, then the value is read from stdin. nuxeoctl config [--get] <key>.. [-d [<categories>]|-q] Get value for the given key(s). nuxeoctl config [--get-regexp] <regexp>.. [-d [<categories>]|-q] Get value for the keys matching the given regular expression(s).
See "nuxeoctl help" and online documentation: ADMINDOC/nuxeoctl and Control Panel Usage and ADMINDOC/Sensitive Configuration Data Encryption.