Andy thanks for pointing out configJsonIn, that will work just as well. Thanks for all the hard work with the toolkit its very cool.
On Thu, Sep 20, 2018 at 9:32 PM Andy LoPresto <alopre...@apache.org> wrote: > Juan, > > The client/server mode does not expose as many command-line options as > standalone mode, but you can provide a config.json file which contains > values to use and use --configJsonIn to specify the path. See [1] for more > details. > > I am currently working on NIFI-5485 [2] and can try to improve the > command-line flags for client/server mode as an add-on ticket [3]. > > [1] > https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#client > [2] https://issues.apache.org/jira/browse/NIFI-5485 > [3] https://issues.apache.org/jira/browse/NIFI-5620 > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Sep 20, 2018, at 3:41 PM, Juan Sequeiros <helloj...@gmail.com> wrote: > > Hello all, > > Using nifitoolkit bin/tls-toolkit.sh > > While using client / server mode ( CA issuer ) > Is there any way to pass it parameters like the ones using standalone mode? > > Want to be able to set the password through the command line > Similar to how I can on standalone mode > EX: > > Do this equivalent through toolkit with client option: > > Thanks! > > tls-toolkit.sh standalone -n 'SomeHost' -K 'KeyStorePassword' -P > 'TrustPassword' -S 'KeyPassword' > > > -- Juan Carlos Sequeiros
