[
https://issues.apache.org/jira/browse/NIFI-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200462#comment-17200462
]
Andy LoPresto commented on NIFI-7836:
-------------------------------------
Hi David, are you proposing to implement this or just requesting it? There are
outstanding tickets for refactoring the generic {{EncryptContent}} processor to
split out symmetric key management to controller services, PGP
encryption/decryption/signing/verification to separate processors sharing key
management controller services, etc. I think it makes sense to come up with a
standard organizational and naming approach and then implement each of the
algorithm families in that way.
> Add Encrypt and Decrypt CMS Processors and Services
> ---------------------------------------------------
>
> Key: NIFI-7836
> URL: https://issues.apache.org/jira/browse/NIFI-7836
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: David Handermann
> Priority: Major
>
> The purpose of this issue is to add new Processors and Controller Services
> supporting encryption and decryption using Cryptographic Message Syntax as
> defined in RFC 5652.
> CMS provides the underlying specification for S/MIME messages and also
> supports encryption and decryption using X.509 certificates. Standard Java
> Key Stores can be used to support encrypting messages for one or more
> recipients. Decrypting messages can also be supported based on matching
> certificate serial number and issuer attributes.
> The current EncryptContent Processor supports encryption using passwords and
> PGP keys, but does not support encryption using X.509 certificates. New
> Processors for encryption and decryption would support encryption using X.509
> certificates using CMS classes in the Bouncy Castle library. New Controller
> Services would provide access to certificate and private key information from
> standard Java Key Stores.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
