[
https://issues.apache.org/jira/browse/NIFI-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665339#comment-15665339
]
ASF subversion and git services commented on NIFI-3032:
-------------------------------------------------------
Commit 4d1bcc808f5c75a7b7bb3a42d79b5a8f28c44d4f in nifi's branch
refs/heads/master from [~alopresto]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4d1bcc8 ]
NIFI-3032 Resolved issue where multiple invocations of
NiFiPropertiesLoader.withKey() used cached key.
Added unit tests and resources.
NIFI-3032 Fixed bug in AESSensitivePropertyProvider#getIdentifierKey where the
result was always the max available key size, not the size of the current key.
Added unit test.
This closes #1220
Signed-off-by: Bryan Rosander <brosan...@apache.org>
> NiFiPropertiesLoader can cache stale key after migration
> --------------------------------------------------------
>
> Key: NIFI-3032
> URL: https://issues.apache.org/jira/browse/NIFI-3032
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Blocker
> Labels: encryption, security
> Fix For: 1.1.0
>
>
> [~bryanrosan...@gmail.com] discovered an issue where the
> {{NiFiPropertiesLoader}} can be initialized with a static
> {{SensitivePropertyProviderFactory}} containing a specific {{key}}, and then
> when {{NiFiPropertiesLoader.withKey()}} is called with a different key, the
> factory is not refreshed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
