You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2022/05/04 17:55:00 UTC
[jira] [Updated] (NIFI-9988) Property Decryption Fails for Authorizers and Login Identity Providers
[ https://issues.apache.org/jira/browse/NIFI-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-9988:
-----------------------------------
Status: Patch Available (was: Open)
> Property Decryption Fails for Authorizers and Login Identity Providers
> ----------------------------------------------------------------------
>
> Key: NIFI-9988
> URL: https://issues.apache.org/jira/browse/NIFI-9988
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.1
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Recent changes to restructure Sensitive Property Provider class-loading involved changes to the Authorizers and Login Identity Providers configuration classes. Part of the adjustment involved refactoring the resolution of {{encryption}} attribute values to internal {{Protection Scheme}} supported values.
> As a result of this change, calls to {{ProtectionSchemeResolver.getProtectionScheme()}} fail with a {{SensitivePropertyProtectionException}} indicating that the requested scheme, such as {{aes/gcm/256}} is not supported.
> The {{StandardProtectionSchemeResolver}} should be adjusted to match the requested scheme string against both the Protection Scheme Name, as well as the Protection Scheme Path. The {{StandardSensitivePropertyProviderFactory}} already follows a similar strategy. This approach will allow decryption to work as expected.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)