[
https://issues.apache.org/jira/browse/NIFI-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136502#comment-18136502
]
Marcos-Dimitris Fetcu commented on NIFI-16514:
----------------------------------------------
[~exceptionfactory] Sure, here is my output:
{code:java}
:secret key packet:
version 4, algo 1, created 1793624258, expires 0
skey[0]: [3072 bits]
skey[1]: [17 bits]
iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: xxxxxxx
protect count: 12058624 (215)
protect IV: xx xx xx xx xx xx
encrypted stuff follows
keyid: XXXXXXXXXX
:user ID packet: "nifi-flow (NiFi) <[email protected]>"
:signature packet: algo 1, keyid XXXXXXXXXX
version 4, created 1793624258, md5len 0, sigclass 0x13
digest algo 2, begin of digest 86 4b
hashed subpkt 2 len 4 (sig created 2026-11-02)
hashed subpkt 27 len 1 (key flags: 03)
hashed subpkt 9 len 4 (key expires after 1y0d0h0m)
hashed subpkt 11 len 6 (pref-sym-algos: 9 8 7 3 2 1)
hashed subpkt 21 len 5 (pref-hash-algos: 8 2 9 10 11)
hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
subpkt 16 len 8 (issuer key ID XXXXXXXXXX)
data: [3070 bits]
:secret sub key packet:
version 4, algo 1, created 1793624258, expires 0
skey[0]: [3072 bits]
skey[1]: [17 bits]
iter+salt S2K, algo: 3, SHA1 protection, hash: 2, salt: xxxxxxx
protect count: 12058624 (215)
protect IV: 4c e2 62 dc 3e 9e b5 d3
encrypted stuff follows
keyid: ZZZZZZZZZZZ
:signature packet: algo 1, keyid XXXXXXXXXX
version 4, created 1793624258, md5len 0, sigclass 0x18
digest algo 2, begin of digest 4b 18
hashed subpkt 2 len 4 (sig created 2026-11-02)
hashed subpkt 27 len 1 (key flags: 0C)
hashed subpkt 9 len 4 (key expires after 1y0d0h0m)
subpkt 16 len 8 (issuer key ID XXXXXXXXXX)
data: [3067 bits]{code}
> StandardPGPPrivateKeyService Service Error On Startup
> -----------------------------------------------------
>
> Key: NIFI-16514
> URL: https://issues.apache.org/jira/browse/NIFI-16514
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 2.12.0
> Environment: Linux CentOS 7
> Reporter: Marcos-Dimitris Fetcu
> Priority: Major
>
> I recently migrated from NiFi 1.x to latest NiFi 2.12.0.
> During the upgrade process I had to replace some deprecated components.
> In my flow I was using an *EncryptContent* processor set up for decryption,
> and {*}I replaced it with the current processor for decryption:
> DecryptContentPGP{*}.
> Additionally, to the DecryptContentPGP component *I had also to configure a
> StandardPGPPrivateKeyService* service and
> *AzureKeyVaultSecretsParameterProvider parameter provider* for the PGP
> password.
> My configuration is the following:
> *DecryptContentPGP:*
> Decryption Strategy: DECRYPTED
> Passphrase: No value set
> Private Key Service: StandardPGPPrivateKeyService
> *StandardPGPPrivateKeyService:*
> Keyring File: $(the_path_where_the_keyring_file_is_stored)
> Keyring: No value set
> Key Password:
> #\{parameter_variable_fetched_from_azure_containing_the_decryption_password}
> Here for testing purposes, I am supposed to stop and restart NiFi very often.
> And *after a fresh startup I notice that each time I have a one-time error
> related to StandardPGPPrivateKeyService failing to load the Keyring file.* I
> mention that the keyring file is available at the specified path and is not
> loaded dynamically at each start, so at the time the service is starting I
> know that there does not exist a problem with that file being unavailable.
> ERROR Message:
> Could not start
> StandardControllerServiceNode[service=StandardPGPPrivateKeyService[id=UUID],
> name=StandardPGPPrivateKeyService, active=true] due to
> java.util.concurrent.ExecutionException: java.lang.IllegalStateException:
> Enabling
> StandardControllerServiceNode[service=StandardPGPPrivateKeyService[id=UUID],
> name=StandardPGPPrivateKeyService, active=true] failed: Validation Status
> [INVALID] Errors ['Keyring File' is invalid because Reading Secret Keyring
> File Failed: Reading Secret Keyring File [/path/to/file/pgp_private_key_file]
> Failed, 'StandardPGPPrivateKeyService' is invalid because No Private Keys
> Read from [Keyring File] or [Keyring]]
> Regarding to *AzureKeyVaultSecretsParameterProvider* I am able to see in the
> logs that the parameters are fetched successfully before this ERROR is
> thrown, at least with one second earlier. Meaning, according to the logs the
> parameter secret is available when it attempts to enable the
> *StandardPGPPrivateKeyService.*
> Also, the *StandardPGPPrivateKeyService* is enabled successfully around 10
> seconds after the given ERROR. Therefore, I consider this one-time ERROR as
> being a bug.
> Could you please address this issue?
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
