[
https://issues.apache.org/jira/browse/NIFI-16327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18117663#comment-18117663
]
Nicolas Chauvet commented on NIFI-16327:
----------------------------------------
It worth noting that:
* In Nifi-2.8 there is a need to fill the namespace in both ClientService and
parameter Provider (using a prefix namespace key/value path
my_namespace/my_secret)
* In Nifi-2.12 there is only a need to fill the namespace in the
ClientService. It doesn't work anymore if the namespace is specified as a
prefix in parameter provider.
Out of curiosity, is there any public report for Unit Tests running under the
Apache infrastructure ?
> HC Vault namespace propagation error on non-token Authentication
> ----------------------------------------------------------------
>
> Key: NIFI-16327
> URL: https://issues.apache.org/jira/browse/NIFI-16327
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 2.10.0, 2.11.0
> Reporter: Nicolas Chauvet
> Priority: Trivial
> Labels: vault
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The vault.namespace property was not propagated to login requests for CERT
> and other non-TOKEN authentication methods, because NIFI-16013 removed the
> restTemplateBuilder override that added the X-Vault-Namespace header. Spring
> Vault 4.1 builds the login VaultClient through that builder, so the login
> request was sent to the Vault root namespace.
> This is a regression introduced in 2.10.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
