Member since
03-10-2017
170
Posts
80
Kudos Received
32
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1168 | 08-12-2024 08:42 AM | |
| 1995 | 05-30-2024 04:11 AM | |
| 2574 | 05-29-2024 06:58 AM | |
| 1735 | 05-16-2024 05:05 AM | |
| 1328 | 04-23-2024 01:46 AM |
08-11-2025
09:05 PM
1 Kudo
This article provides detailed steps about Encrypting and Decrypting files using the Pretty Good Privacy (PGP) algorithm in NiFi
Steps involve :
Setting up GPG private key and Public key
Creating NiFi flow
Setting up GPG private key and Public key
Set up the GPG home directory export GNUPGHOME=/tmp/gnupg
Generate a private and public key with a user ID gpg --full-generate-key
gpg (GnuPG) 2.2.20; Copyright (C) 2020 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Please select what kind of key you want:
(1) RSA and RSA (default)
(2) DSA and Elgamal
(3) DSA (sign only)
(4) RSA (sign only)
(14) Existing key from card
Your selection? 1
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 2048
Requested keysize is 2048 bits
Please specify how long the key should be valid.
0 = key does not expire
<n> = key expires in n days
<n>w = key expires in n weeks
<n>m = key expires in n months
<n>y = key expires in n years
Key is valid for? (0) 0
Key does not expire at all
Is this correct? (y/N) y
GnuPG needs to construct a user ID to identify your key.
Real name: TestXYZ
Email address: test@example.com
Comment:
You selected this USER-ID:
"TestXYZ <test@example.com>"
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
There will be a prompt to enter a passphrase, which will be used later in the configuration
There will be 4 files created under /tmp/gnupg
Create a public and private keyring file in ASCII format
For the public keyring file, run the following command gpg --export --armor --output testexample.gpg.pub test@example.com
For the Private keyring file, run the following command gpg --export-secret-keys --armor --output testexample.gpg.asc test@example.com
We would have two new files created under /tmp/gnupg
Creating NiFi flow
At this point, all set to create flow design using EncryptContentPGP and DecryptContentPGP, which use controller services StandardPGPPublicKeyService and StandardPGPPrivateKeyService
EncryptContentPGP configured with StandardPGPPublicKeyService
DecryptContentPGP with StandardPGPPrivateKeyService Note: In StandardPGPPrivateKeyService passphrase needs to be entered, which was set while running the gpg --full-generate-key command
Snapshot from working flow tested with .csv and .xlsx files
... View more
Labels:
11-06-2024
05:31 AM
Hello, you can see other solution here: https://community.cloudera.com/t5/Support-Questions/Nifi-Execute-Groovy-Script/m-p/344265#M234128
... View more
08-19-2024
07:03 AM
Hi @ckumar , I couldn't find the command, would it be in the parcels path as shown in the attached printout?
... View more
08-13-2024
05:30 PM
1 Kudo
Thanks kumar. Yeah we found that content repository file was not persistent in our container. After changing that , it works.
... View more
08-12-2024
07:54 PM
1 Kudo
Hi Ckumar, recently I can not open the UI because the error of 403 when I check the nifi-request.log file also. I think all error come from same reason.
... View more
08-09-2024
09:17 PM
thank u very much. that helped me
... View more
06-14-2024
07:46 AM
1 Kudo
@Alexy Without seeing your logs, I have no idea which NiFi classes are producing the majority of your logging. But logback is functioning exactly as you have it configured. Each time the nifi-app.log reaches 500 MB within a single day it is compressed and rolled using an incrementing number. I would suggest changing the log level for the base class "org.apache.nifi" from INFO to WARN. The bulk of all NiFi classes begin with org.apache.nifi and by changing this to WARN to you will only see ERROR and WARN level log output from the bulk of the ora.apache.nifi.<XYZ...> classes. <logger name="org.apache.nifi" level="WARN"/> Unless you have a lot of exception happening within your NiFi processor components used in your dataflow(s), this should have significant impact on the amount of nifi-app.log logging being produced. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
06-10-2024
10:32 PM
@Naveen_Sagar, were you able to resolve this issue? If you were, could you please share the solution so that it can help others? If you still have concerns, could you please provide the information that @ckumar has requested?
... View more
06-06-2024
07:12 AM
@alan18080 NiFi-Registry only pushes to the GitFlowPersistenceProvider while running. NIFi-Registry will only read from Git on startup. The GitFlowPersistence Provider also only contains the flow definitions for the version controlled process groups. Each NiFi-Registry has a metadata database maintains the knowledge of which buckets exist, which versioned items belong to which buckets, as well as the version history for each item. So if you are trying to share a single Git Repo across multiple running NiFi-Registry instances this will explain why you are seeing missing versions at times across your multiple instances. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt
... View more
06-02-2024
10:15 PM
@Naveen_Sagar, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.
... View more