[
https://issues.apache.org/jira/browse/NIFI-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated NIFI-91:
----------------------------
Description:
Provide UI functionality to allow changing of the sensitive property properties
on the fly, during which any of the necessary mechanics behind the scenes are
also provided.
Currently, a default and hardcoded sensitive properties key is used to
facilitate new users getting the application up and running. Should a user
make use of extensions that have sensitive properties, they are currently bound
to that value should they wish to adjust the key being used via the
nifi.properties file. This additionally requires a restart.
Previous description below:
Sensitive properties are created with a default key if none is specified via
nifi.properties. This was done to provide a way for users to get the
application running out of the box. However, if users configure sensitive
properties there is not a good way for them to recover/convert these items to a
new key should one be desired.
This utility would aid in the above transformation process.
was:
Sensitive properties are created with a default key if none is specified via
nifi.properties. This was done to provide a way for users to get the
application running out of the box. However, if users configure sensitive
properties there is not a good way for them to recover/convert these items to a
new key should one be desired.
This utility would aid in the above transformation process.
> Allow the changing of sensitive property properties via the UI
> --------------------------------------------------------------
>
> Key: NIFI-91
> URL: https://issues.apache.org/jira/browse/NIFI-91
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Reporter: Matt Gilman
> Priority: Minor
>
> Provide UI functionality to allow changing of the sensitive property
> properties on the fly, during which any of the necessary mechanics behind the
> scenes are also provided.
> Currently, a default and hardcoded sensitive properties key is used to
> facilitate new users getting the application up and running. Should a user
> make use of extensions that have sensitive properties, they are currently
> bound to that value should they wish to adjust the key being used via the
> nifi.properties file. This additionally requires a restart.
> Previous description below:
> Sensitive properties are created with a default key if none is specified via
> nifi.properties. This was done to provide a way for users to get the
> application running out of the box. However, if users configure sensitive
> properties there is not a good way for them to recover/convert these items to
> a new key should one be desired.
> This utility would aid in the above transformation process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
