[jira] [Updated] (NIFI-13296) Deprecate Kerberos SPNEGO Authentication for Removal
[ https://issues.apache.org/jira/browse/NIFI-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13296: Status: Patch Available (was: Open) > Deprecate Kerberos SPNEGO Authentication for Removal > > > Key: NIFI-13296 > URL: https://issues.apache.org/jira/browse/NIFI-13296 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NiFi 0.6.0 added Kerberos authentication with > [SPNEGO|https://en.wikipedia.org/wiki/SPNEGO] as a framework feature based on > Spring Security Kerberos. Although Spring Security Kerberos continues to be > maintained, SPNEGO authentication is not common, requiring specialized > [client browser > configuration|https://docs.spring.io/spring-security-kerberos/docs/current/reference/html/browserspnegoconfig.html] > for access. As noted in the linked instructions, popular web browsers do not > support SPNEGO in the default configuration, and Google Chrome requires > either a custom policy or launch from the command line with arguments that > list permitted DNS names. > Based on these considerations, and in light of more common Single Sign-On > strategies using OpenID Connect and SAML 2, NiFi framework support for > Kerberos authentication with SPNEGO should be deprecated for subsequent > removal in NiFi 2. > This deprecation should not impact the Kerberos Login Identity Provider, > which continues to support username and password authentication based on the > form-based login process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13297) Remove Kerberos SPNEGO Authentication
[ https://issues.apache.org/jira/browse/NIFI-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13297: Status: Patch Available (was: Open) > Remove Kerberos SPNEGO Authentication > - > > Key: NIFI-13297 > URL: https://issues.apache.org/jira/browse/NIFI-13297 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > As described in NIFI-13296, authentication with Kerberos using > [SPNEGO|https://en.wikipedia.org/wiki/SPNEGO] should be removed from the main > branch for NiFi 2. > The Kerberos Login Identity Provider should be considered separately, and > could be maintained indepently without impacting NiFi framework capabilities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13297) Remove Kerberos SPNEGO Authentication
David Handermann created NIFI-13297: --- Summary: Remove Kerberos SPNEGO Authentication Key: NIFI-13297 URL: https://issues.apache.org/jira/browse/NIFI-13297 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann As described in NIFI-13296, authentication with Kerberos using [SPNEGO|https://en.wikipedia.org/wiki/SPNEGO] should be removed from the main branch for NiFi 2. The Kerberos Login Identity Provider should be considered separately, and could be maintained indepently without impacting NiFi framework capabilities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13296) Deprecate Kerberos SPNEGO Authentication for Removal
David Handermann created NIFI-13296: --- Summary: Deprecate Kerberos SPNEGO Authentication for Removal Key: NIFI-13296 URL: https://issues.apache.org/jira/browse/NIFI-13296 Project: Apache NiFi Issue Type: Improvement Reporter: David Handermann Assignee: David Handermann NiFi 0.6.0 added Kerberos authentication with [SPNEGO|https://en.wikipedia.org/wiki/SPNEGO] as a framework feature based on Spring Security Kerberos. Although Spring Security Kerberos continues to be maintained, SPNEGO authentication is not common, requiring specialized [client browser configuration|https://docs.spring.io/spring-security-kerberos/docs/current/reference/html/browserspnegoconfig.html] for access. As noted in the linked instructions, popular web browsers do not support SPNEGO in the default configuration, and Google Chrome requires either a custom policy or launch from the command line with arguments that list permitted DNS names. Based on these considerations, and in light of more common Single Sign-On strategies using OpenID Connect and SAML 2, NiFi framework support for Kerberos authentication with SPNEGO should be deprecated for subsequent removal in NiFi 2. This deprecation should not impact the Kerberos Login Identity Provider, which continues to support username and password authentication based on the form-based login process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13295) Remove Apache Knox SSO Integration
[
https://issues.apache.org/jira/browse/NIFI-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13295:
Status: Patch Available (was: Open)
> Remove Apache Knox SSO Integration
> --
>
> Key: NIFI-13295
> URL: https://issues.apache.org/jira/browse/NIFI-13295
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As described in NIFI-13294, custom Single Sign-On integration with Apache
> Knox based on JSON Web Tokens and custom public key verification should be
> removed from the main branch. [Proxy
> access|https://knox.apache.org/books/knox-1-6-0/user-guide.html#Nifi+UI]
> through Apache Knox should remain supported through the non-product-specific
> {{X-ProxiedEntitiesChain}} HTTP header strategy with X.509 client
> certificates.
> OpenID Connect and SAML 2 integration continue to provide standards-based
> Single Sign-On solutions, obviating the need for custom cookie-based token
> communication and verification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13294) Deprecate Apache Knox SSO Integration for Removal
[
https://issues.apache.org/jira/browse/NIFI-13294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13294:
Status: Patch Available (was: Open)
> Deprecate Apache Knox SSO Integration for Removal
> -
>
> Key: NIFI-13294
> URL: https://issues.apache.org/jira/browse/NIFI-13294
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NiFi 1.4.0 introduced support for authentication with Apache Knox [Single
> Sign-On|https://knox.apache.org/books/knox-1-6-0/user-guide.html#SSO+Cookie+Provider]
> based on JSON Web Tokens provided through a cookie and verified using a
> configurable public key.
> Separate from Apache Knox SSO authentication, Apache Knox itself provides
> [gateway
> access|https://knox.apache.org/books/knox-1-6-0/user-guide.html#Nifi+UI] as a
> proxy using the {{X-ProxiedEntitiesChain}} HTTP Header. Proxy access should
> remain supported as it is part of the X.509 client certificate authentication
> strategy. Deployment patterns based on Apache Knox gateway access work
> without any features or configuration properties specific to Knox.
> With the implementation of standards-based Single Sign-On using OpenID
> Connect and SAML 2, custom cookie-based SSO with Apache Knox should be
> deprecated for removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-13295) Remove Apache Knox SSO Integration
David Handermann created NIFI-13295:
---
Summary: Remove Apache Knox SSO Integration
Key: NIFI-13295
URL: https://issues.apache.org/jira/browse/NIFI-13295
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
As described in NIFI-13294, custom Single Sign-On integration with Apache Knox
based on JSON Web Tokens and custom public key verification should be removed
from the main branch. [Proxy
access|https://knox.apache.org/books/knox-1-6-0/user-guide.html#Nifi+UI]
through Apache Knox should remain supported through the non-product-specific
{{X-ProxiedEntitiesChain}} HTTP header strategy with X.509 client certificates.
OpenID Connect and SAML 2 integration continue to provide standards-based
Single Sign-On solutions, obviating the need for custom cookie-based token
communication and verification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-13294) Deprecate Apache Knox SSO Integration for Removal
David Handermann created NIFI-13294:
---
Summary: Deprecate Apache Knox SSO Integration for Removal
Key: NIFI-13294
URL: https://issues.apache.org/jira/browse/NIFI-13294
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
NiFi 1.4.0 introduced support for authentication with Apache Knox [Single
Sign-On|https://knox.apache.org/books/knox-1-6-0/user-guide.html#SSO+Cookie+Provider]
based on JSON Web Tokens provided through a cookie and verified using a
configurable public key.
Separate from Apache Knox SSO authentication, Apache Knox itself provides
[gateway
access|https://knox.apache.org/books/knox-1-6-0/user-guide.html#Nifi+UI] as a
proxy using the {{X-ProxiedEntitiesChain}} HTTP Header. Proxy access should
remain supported as it is part of the X.509 client certificate authentication
strategy. Deployment patterns based on Apache Knox gateway access work without
any features or configuration properties specific to Knox.
With the implementation of standards-based Single Sign-On using OpenID Connect
and SAML 2, custom cookie-based SSO with Apache Knox should be deprecated for
removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-4586) Wrong URI can be created by ApplicationResource when X-Proxy and X-Forwarded headers exist in the request
[ https://issues.apache.org/jira/browse/NIFI-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-4586. Resolution: Cannot Reproduce > Wrong URI can be created by ApplicationResource when X-Proxy and X-Forwarded > headers exist in the request > - > > Key: NIFI-4586 > URL: https://issues.apache.org/jira/browse/NIFI-4586 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.4.0 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Critical > > While testing support for Knox proxying to a secure NiFi cluster, I was > unable to modify/move components after creating them. This is being caused > by behavior in ApplicationResource#generateResourceUri, which attempts to get > the first header value in the request between the X-Proxy* and X-Forwarded* > headers. > If the request has both sets of headers, the code will prioritize the > X-Proxy* headers, and will generate the URI with those values. Since Knox > sets the X-Forwarded* headers, if the X-Proxy* headers are on the request, > the headers supplied by Knox will be ignored. > The NiFi UI will then attempt to access the URI generated with the X-Proxied* > header values. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-5602) Enable user authentication with Apache Knox
[ https://issues.apache.org/jira/browse/NIFI-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-5602. Resolution: Won't Fix > Enable user authentication with Apache Knox > > > Key: NIFI-5602 > URL: https://issues.apache.org/jira/browse/NIFI-5602 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Sarthak >Priority: Major > > Enable user authentication with Apache Knox -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-4430) Investigate Apache Knox SSO Logout
[ https://issues.apache.org/jira/browse/NIFI-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-4430. Resolution: Won't Fix > Investigate Apache Knox SSO Logout > -- > > Key: NIFI-4430 > URL: https://issues.apache.org/jira/browse/NIFI-4430 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Priority: Minor > > Currently, when integrating with Knox for SSO a cookie is added during the > login sequence. This cookie is validated to authenticate the user in NiFi. We > should investigate if and how we should offer a logout option for the end > user. > - Should logout be a Knox function? > - Should we remove the cookie that Knox generated? > - Do we need to invoke any function in Knox to complete the logout? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-4986) Knox SSO token expiry handling (NiFi + Knox + SSO)
[ https://issues.apache.org/jira/browse/NIFI-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-4986. Resolution: Won't Fix > Knox SSO token expiry handling (NiFi + Knox + SSO) > -- > > Key: NIFI-4986 > URL: https://issues.apache.org/jira/browse/NIFI-4986 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.5.0 >Reporter: Jeff Storck >Priority: Major > > When NiFi is proxied through Knox using the SSOCookieProvider, the NiFi UI > can not determine when the Knox SSO token has expired. > The NiFI UI attempts to make API calls through Knox via XHRs > (XMLHttpRequests), which end up receiving the Knox SSO login page as the > response if the Knox SSO token has expired. Knox will be patched for this > via [https://issues.apache.org/jira/browse/KNOX-1210|KNOX-1210], and a 401 > will be returned by the call to Knox if the token has expired. > The NiFi UI will need a way to allow the user to log in through the KnoxSSO > again after receiving a 401 in this scenario. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13293) Upgrade Spring Security to 6.3.0
[ https://issues.apache.org/jira/browse/NIFI-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13293: Status: Patch Available (was: Open) > Upgrade Spring Security to 6.3.0 > > > Key: NIFI-13293 > URL: https://issues.apache.org/jira/browse/NIFI-13293 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Spring Security dependencies should be upgraded to > [6.3.0|https://github.com/spring-projects/spring-security/releases/tag/6.3.0] > to incorporate various bug fixes and feature improvements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13293) Upgrade Spring Security to 6.3.0
David Handermann created NIFI-13293: --- Summary: Upgrade Spring Security to 6.3.0 Key: NIFI-13293 URL: https://issues.apache.org/jira/browse/NIFI-13293 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: David Handermann Assignee: David Handermann Spring Security dependencies should be upgraded to [6.3.0|https://github.com/spring-projects/spring-security/releases/tag/6.3.0] to incorporate various bug fixes and feature improvements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13265) Remove the instantiation of Object arrays for arguments in ComponentLog log statements
[ https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849333#comment-17849333 ] David Handermann commented on NIFI-13265: - Yes, this should be applicable to all SLF4J Logger calls. > Remove the instantiation of Object arrays for arguments in ComponentLog log > statements > -- > > Key: NIFI-13265 > URL: https://issues.apache.org/jira/browse/NIFI-13265 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > > There are still classes after the changes in NIFI-12075 and NIFI-12076 which > instantiate an Object array for ComponentLog log statements. This ticket aims > to remove those instantiations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13231) Update GitHubFlowRegistryClient to generate App Installation Token
[ https://issues.apache.org/jira/browse/NIFI-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849309#comment-17849309 ] David Handermann commented on NIFI-13231: - Thanks [~vanshchaudhary]. If you have any questions during the implementation, feel free to raise here, otherwise I can review the pull request when you have it ready. The GitHub API library includes a [JWTTokenProvider|https://github.com/hub4j/github-api/blob/main/src/main/java/org/kohsuke/github/extras/authorization/JWTTokenProvider.java] that handles the process of generating a JWT from an Application ID and Private Key, so that should be helpful. As documented in that class, it does not perform any kind of caching, but it does incorporate time-based validity checking, so it should be possible to create an use an instance of the class in the GitHub Flow Registry Client. > Update GitHubFlowRegistryClient to generate App Installation Token > -- > > Key: NIFI-13231 > URL: https://issues.apache.org/jira/browse/NIFI-13231 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Brian Ghigiarelli >Assignee: Vansh Chaudhary >Priority: Major > > The new GitHubFlowRegistryClient accepts two types of authentication: > # Personal Access Token > # App Installation Token > The App Installation Token requires the user to input the token as a > property, then uses that to communicate with GitHub. However, this token is > short-lived and would require frequent updates (~hourly). > Instead of directly providing the token, the GitHubFlowRegistryClient should > accept as properties: > # App ID > # Private Key (PEM text format) > and use these values to generate a short-lived token, following the guide at > https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app#generating-a-json-web-token-jwt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849085#comment-17849085 ] David Handermann commented on NIFI-13191: - Thanks for following up [~chien]. The processor was using an older version of the AWS SDK 1, and the level of abstraction was not a good fit for a maintainable Processor. The binaries and source for earlier versions are available, which is an option if you would like to maintain your own version. On the other hand, it would be helpful to create new Jira issues describing the more specific Processors, such as one for sending messages using Amazon SES. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13231) Update GitHubFlowRegistryClient to generate App Installation Token
[ https://issues.apache.org/jira/browse/NIFI-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848974#comment-17848974 ] David Handermann commented on NIFI-13231: - [~vanshchaudhary] are you planning on working on this soon? I was also planning take a look at implementing this change, but if you are familiar with the properties and operations required for implementation, I would be willing to review. > Update GitHubFlowRegistryClient to generate App Installation Token > -- > > Key: NIFI-13231 > URL: https://issues.apache.org/jira/browse/NIFI-13231 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Brian Ghigiarelli >Assignee: Vansh Chaudhary >Priority: Major > > The new GitHubFlowRegistryClient accepts two types of authentication: > # Personal Access Token > # App Installation Token > The App Installation Token requires the user to input the token as a > property, then uses that to communicate with GitHub. However, this token is > short-lived and would require frequent updates (~hourly). > Instead of directly providing the token, the GitHubFlowRegistryClient should > accept as properties: > # App ID > # Private Key (PEM text format) > and use these values to generate a short-lived token, following the guide at > https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app#generating-a-json-web-token-jwt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13259) Publish NiFi Stateless Assembly to Maven
[ https://issues.apache.org/jira/browse/NIFI-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13259. - Fix Version/s: 2.0.0-M4 Assignee: Bob Paulin Resolution: Fixed > Publish NiFi Stateless Assembly to Maven > > > Key: NIFI-13259 > URL: https://issues.apache.org/jira/browse/NIFI-13259 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bob Paulin >Assignee: Bob Paulin >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > I'd like to do some integration test work with flow files using the nifi > stateless assembly zip. Would like this published to maven to allow this to > work using unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13255) Replace deprecated io.netty.handler.ssl.JdkSslContext constructor with API suggested replacement
[ https://issues.apache.org/jira/browse/NIFI-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13255: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace deprecated io.netty.handler.ssl.JdkSslContext constructor with API > suggested replacement > > > Key: NIFI-13255 > URL: https://issues.apache.org/jira/browse/NIFI-13255 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix should be applied to > nifi-extension-bundles/nifi-graph-bundle/nifi-other-graph-services/src/main/java/org/apache/nifi/graph/TinkerpopClientService.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13259) Publish NiFi Stateless Assembly to Maven
[ https://issues.apache.org/jira/browse/NIFI-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13259: Summary: Publish NiFi Stateless Assembly to Maven (was: Publish NiFi Stateless to Maven) > Publish NiFi Stateless Assembly to Maven > > > Key: NIFI-13259 > URL: https://issues.apache.org/jira/browse/NIFI-13259 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Bob Paulin >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > I'd like to do some integration test work with flow files using the nifi > stateless assembly zip. Would like this published to maven to allow this to > work using unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13259) Publish NiFi Stateless Assembly to Maven
[ https://issues.apache.org/jira/browse/NIFI-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13259: Affects Version/s: (was: 2.0.0-M3) > Publish NiFi Stateless Assembly to Maven > > > Key: NIFI-13259 > URL: https://issues.apache.org/jira/browse/NIFI-13259 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bob Paulin >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > I'd like to do some integration test work with flow files using the nifi > stateless assembly zip. Would like this published to maven to allow this to > work using unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13275) Remove web.xml from nifi-web-frontend
[ https://issues.apache.org/jira/browse/NIFI-13275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13275: Status: Patch Available (was: Open) > Remove web.xml from nifi-web-frontend > - > > Key: NIFI-13275 > URL: https://issues.apache.org/jira/browse/NIFI-13275 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Following recent changes in nifi-web-frontend to remove the need for Servlet > Filters, the Servlet configuration in web.xml is no longer needed. With the > frontend code relying exclusively on REST API calls to nifi-web-api, the > web.xml configuration and nifi-web-utils dependencies are no longer required. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13275) Remove web.xml from nifi-web-frontend
David Handermann created NIFI-13275: --- Summary: Remove web.xml from nifi-web-frontend Key: NIFI-13275 URL: https://issues.apache.org/jira/browse/NIFI-13275 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: David Handermann Assignee: David Handermann Following recent changes in nifi-web-frontend to remove the need for Servlet Filters, the Servlet configuration in web.xml is no longer needed. With the frontend code relying exclusively on REST API calls to nifi-web-api, the web.xml configuration and nifi-web-utils dependencies are no longer required. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13227) Upgrade Spring to 6.1.7 and upgrade other common dependencies
[ https://issues.apache.org/jira/browse/NIFI-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13227. - Fix Version/s: 2.0.0-M4 Resolution: Fixed > Upgrade Spring to 6.1.7 and upgrade other common dependencies > - > > Key: NIFI-13227 > URL: https://issues.apache.org/jira/browse/NIFI-13227 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 40m > Remaining Estimate: 0h > > aspectj 1.9.22.1 (1.9.22) > mockito 5.12.0 (5.11.0) > software.amazon.awssdk 2.25.54 (2.25.49) > software.amazon.awssdk 2.25.55 (2.25.49) > com.amazonaws 1.12.724 (719) > com.amazonaws 1.12.725 (719) > com.slack.api 1.39.2 (from 1.39.0) > swagger-annotations 2.2.22 (2.2.21) > mockftpserver 3.2.0 (from 3.1.0) > org.springframework 6.1.6 6.1.7 > subethasmtp 7.1.1 (from 7.0.2) > reactor-core/test 3.6.6 (from 3.6.5) > spring-retry 2.0.6 > reactor-netty-http 1.1.19 (18) > com.google.cloud libraries bom 26.39.0 26.38.0 > flyway 10.12.0 -> 10.13.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13227) Upgrade Spring to 6.1.7 and upgrade other common dependencies
[ https://issues.apache.org/jira/browse/NIFI-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13227: Summary: Upgrade Spring to 6.1.7 and upgrade other common dependencies (was: Bump aspectj and mockito and various dependencies) > Upgrade Spring to 6.1.7 and upgrade other common dependencies > - > > Key: NIFI-13227 > URL: https://issues.apache.org/jira/browse/NIFI-13227 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > aspectj 1.9.22.1 (1.9.22) > mockito 5.12.0 (5.11.0) > software.amazon.awssdk 2.25.54 (2.25.49) > software.amazon.awssdk 2.25.55 (2.25.49) > com.amazonaws 1.12.724 (719) > com.amazonaws 1.12.725 (719) > com.slack.api 1.39.2 (from 1.39.0) > swagger-annotations 2.2.22 (2.2.21) > mockftpserver 3.2.0 (from 3.1.0) > org.springframework 6.1.6 6.1.7 > subethasmtp 7.1.1 (from 7.0.2) > reactor-core/test 3.6.6 (from 3.6.5) > spring-retry 2.0.6 > reactor-netty-http 1.1.19 (18) > com.google.cloud libraries bom 26.39.0 26.38.0 > flyway 10.12.0 -> 10.13.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13254) Replace use of deprecated commons-io BoundedInputStream constructor with API suggestion
[ https://issues.apache.org/jira/browse/NIFI-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13254: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace use of deprecated commons-io BoundedInputStream constructor with API > suggestion > --- > > Key: NIFI-13254 > URL: https://issues.apache.org/jira/browse/NIFI-13254 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > The fix should done in files > # > nifi-extension-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/storage/PutAzureDataLakeStorage.java > # > nifi-extension-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/storage/FetchGCSObject.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13250) Replace deprecated method withRelyingPartyRegistration of org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistration with API suggestion
[
https://issues.apache.org/jira/browse/NIFI-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13250:
Fix Version/s: 2.0.0-M4
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace deprecated method withRelyingPartyRegistration of
> org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistration
> with API suggestion
> ---
>
> Key: NIFI-13250
> URL: https://issues.apache.org/jira/browse/NIFI-13250
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This needs to be changed in
> {code:java}
> nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/sec
> urity/saml2/service/web/StandardRelyingPartyRegistrationResolver.java
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13252) Replace deprecated software.amazon.awssdk.services.sqs.model.ReceiveMessageRequest.Builder argument for attributeNames with API suggestion
[
https://issues.apache.org/jira/browse/NIFI-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13252:
Fix Version/s: 2.0.0-M4
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace deprecated
> software.amazon.awssdk.services.sqs.model.ReceiveMessageRequest.Builder
> argument for attributeNames with API suggestion
> --
>
> Key: NIFI-13252
> URL: https://issues.apache.org/jira/browse/NIFI-13252
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Change must be made in file
> {code:java}
> nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/a
> ws/sqs/GetSQS.java
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13251) Replace deprecated method fromName of com.amazonaws.regions.Regions with API suggestion
[ https://issues.apache.org/jira/browse/NIFI-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13251: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace deprecated method fromName of com.amazonaws.regions.Regions with API > suggestion > --- > > Key: NIFI-13251 > URL: https://issues.apache.org/jira/browse/NIFI-13251 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > Changes need to be made in files > # > nifi-extension-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/util/RegionUtilV1.java > # > nifi-extension-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/java/org/apache/nifi/processors/aws/AbstractAWSCredentialsProviderProcessor.java > # > nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/encryption/ClientSideKMSEncryptionStrategy.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13253) Correct Top Level NOTICE discrepancies
[ https://issues.apache.org/jira/browse/NIFI-13253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13253: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Correct Top Level NOTICE discrepancies > -- > > Key: NIFI-13253 > URL: https://issues.apache.org/jira/browse/NIFI-13253 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > With the latest changes to NIFI.2.0.0-M3 I noticed the following > discrepancies in the top level NOTICE file which should be addressed. > # Lines 7-8 should detail where it is located as other entries in this file > do:nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SoftLimitBoundedByteArrayOutputStream.java > # Lines 10-13 should detail where it is located as other entries in this file > do: > nifi-commons/nifi-property-utils/src/main/java/org/apache/nifi/util/StringUtils.java > # Lines 21-26,31-34 are Hive related items which should be removed as Hive is > no longer supported in NIFI > # Line 46 needs to be changed from > org.apache.nifi.processors.standard.util.jolt.TransformFactory to > org.apache.nifi.jolt.util.TransformFactory > # Line 53 should to be changed from > nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/resources/TestExtractGrok/patterns > to > nifi/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/resources/TestExtractGrok/patterns > # Line 58 should to be changed from Are used in unit tests found in > nifi/nifi-nar-bundles/nifi-enrich-bundle/nifi-enrich > processors/src/test/java/org/apache/nifi/processors/TestGeoEnrichIP.java to > Are used in unit tests found in > nifi/nifi-extension-bundles/nifi-enrich-bundle/nifi-enrich-processors/src/test/java/org/apache/nifi/processors/TestGeoEnrichIP.java > # Lines 60-66 should be removed as there is no class FlowFileTableScan anymore > # Lines 68-71 should be removed as I believe Solr items were removed > # Line 75 does not exist I believe instead of The code can be found > nifi-commons/nifi-security-utils/src/main/java/org/apache/nifi/security/krb/KeytabUser.java > it should be The code can be found > nifi-commons/nifi-security-kerberos/src/main/java/org/apache/nifi/security/krb/KerberosKeytabUser.java > # Also 73-75 is missing a copyright year which I am not sure is an issue or > not. > # Line 88 should be changed from > nifi-nar-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/../wag/client/ > to > nifi-extension-bundles/nifi-aws-bundle/nifi-aws-abstract-processors/src/main/../wag/client/ > # Lines 95-97 should be removed as these classes do not exist > # Lines 99-108 do not mention where the derivative software is used. > # Line 130 should change from > nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-2-6 > processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/CustomKerberosLogin.java > to nifi-extension-bundles/nifi-kafka-bundle/nifi-kafka-2-6 > processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/CustomKerberosLogin.java > # Line 133 should change from Copyright 2002-2023 the original author or > authors. to Copyright 2002-2024 the original author or authors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13259) Publish NiFi Stateless to Maven
[ https://issues.apache.org/jira/browse/NIFI-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13259: Summary: Publish NiFi Stateless to Maven (was: Publish Nifi Stateless to Maven) > Publish NiFi Stateless to Maven > --- > > Key: NIFI-13259 > URL: https://issues.apache.org/jira/browse/NIFI-13259 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Bob Paulin >Priority: Minor > > I'd like to do some integration test work with flow files using the nifi > stateless assembly zip. Would like this published to maven to allow this to > work using unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13259) Publish Nifi Stateless to Maven
[ https://issues.apache.org/jira/browse/NIFI-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13259: Fix Version/s: (was: 2.0.0-M4) > Publish Nifi Stateless to Maven > --- > > Key: NIFI-13259 > URL: https://issues.apache.org/jira/browse/NIFI-13259 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M3 >Reporter: Bob Paulin >Priority: Minor > > I'd like to do some integration test work with flow files using the nifi > stateless assembly zip. Would like this published to maven to allow this to > work using unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12670) JoltTransform processors incorrectly encode/decode text in the Jolt Specification
[
https://issues.apache.org/jira/browse/NIFI-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-12670.
-
Fix Version/s: 2.0.0-M4
Resolution: Fixed
> JoltTransform processors incorrectly encode/decode text in the Jolt
> Specification
> -
>
> Key: NIFI-12670
> URL: https://issues.apache.org/jira/browse/NIFI-12670
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Extensions
>Affects Versions: 2.0.0-M1, 1.24.0, 1.25.0, 2.0.0-M2, 1.26.0, 2.0.0-M3
> Environment: JVM with non-UTF-8 default encoding (e.g. default
> Windows installation)
>Reporter: René Zeidler
>Assignee: Jim Steinebrey
>Priority: Minor
> Labels: encoding, jolt, json, utf8, windows
> Fix For: 2.0.0-M4
>
> Attachments: Jolt_Transform_Encoding_Bug.json,
> Jolt_Transform_Encoding_Bug_M2.json, image-2024-01-25-11-01-15-405.png,
> image-2024-01-25-11-59-56-662.png, image-2024-01-25-12-00-09-544.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Environment
> This issue affects environments where the JVM default encoding is not
> {{{}UTF-8{}}}. Standard Java installations on Windows are affected, as they
> usually use the default encoding {{{}windows-1252{}}}. To reproduce the issue
> on Linux, change the default encoding to {{windows-1252}} by adding the
> following line to your {{{}bootstrap.conf{}}}:
> {quote}{{java.arg.21=-Dfile.encoding=windows-1252}}
> {quote}
> h2. Summary
> The Jolt Specification of both the JoltTransformJSON and JoltTransformRecord
> processors is read interally using the system default encoding, even though
> it is always stored in UTF-8. This causes non-ASCII characters to be garbled
> in the Jolt Specification, resulting in incorrect transformations (missing
> data or garbled keys).
> h2. Steps to reproduce
> # Make sure NiFi runs with a non-UTF-8 default encoding, see "Environment"
> # Create a GenerateFlowFile processor with the following content:
> {quote}{
> "regularString": "string with only ASCII characters",
> "umlautString": "string with non-ASCII characters: ÄÖÜäöüßéèóò",
> "keyWithÜmlaut": "any string"
> }
> {quote}
> # Connect the processor to a JoltTransformJSON and/or JoltTransformRecord
> processor.
> (If using the record based processor, use a default JsonTreeReader and
> JsonRecordSetWriter. The record reader/writer don't affect this bug.)
> Set the Jolt Specification to:
> {quote}[
> {
> "operation": "shift",
> "spec": {
> "regularString": "Remapped to Umlaut ÄÖÜ",
> "umlautString": "Umlaut String",
> "keyWithÜmlaut": "Key with Umlaut"
> }
> }
> ]
> {quote}
> # Connect the outputs of the Jolt processor(s) to funnels to be able to
> observe the result in the queue.
> # Start the Jolt processor(s) and run the GenerateFlowFile processor once.
> The flow should look similar to this:
> !image-2024-01-25-11-01-15-405.png!
> I also attached a JSON export of the example flow.
> # Observe the content of the resulting FlowFile(s) in the queue.
> h3. Expected Result
> !image-2024-01-25-12-00-09-544.png!
> h3. Actual Result
> !image-2024-01-25-11-59-56-662.png!
> * Remapped key containing non-ASCII characters is garbled, since the key
> value originated from the Jolt Specification.
> * The key "{{{}keyWithÜmlaut{}}}" could not be matched at all, since it
> contains non-ASCII characters, resulting in missing data in the output.
> h2. Root Cause Analysis
> Both processors use the
> {{[readTransform|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-jolt-bundle/nifi-jolt-processors/src/main/java/org/apache/nifi/processors/jolt/AbstractJoltTransform.java#L242-L249]}}
> method of {{AbstractJoltTransform}} to read the Jolt Specification property.
> This method uses an
> [{{InputStreamReader}}|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/InputStreamReader.html]
> without specifying an encoding, which then defaults to the default charset
> of the environment. Text properties are [always encoded in
> UTF-8|https://github.com/apache/nifi/blob/89836f32d017d77972a4de09c4e864b0e11899a8/nifi-api/src/main/java/org/apache/nifi/components/resource/StandardResourceReferenceFactory.java#L111].
> When the default charset is not UTF-8, this results in UTF-8 bytes to be
> interpreted in a different encoding when converting to a string, resulting in
> a garbled Jolt Specification being used.
> h2. Workaround
> This issue is not present when any attribute expression language is present
> in the Jolt Specification. Simply adding {{${literal('')}}} anywhere in the
> Jolt Specification works around this issue.
> This happens because [a
[jira] [Commented] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847293#comment-17847293 ] David Handermann commented on NIFI-13191: - [~chien] Can you provide some additional background on how you are using the InvokeAWSGatewayApi Processor, particularly in terms of which AWS service or services you are calling? Based on those details, it may be worth opening a new issue to implement a Processor supporting the particular services. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13219) Conduct Apache NiFi 2.0.0-M3 Release
[ https://issues.apache.org/jira/browse/NIFI-13219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-13219. - Resolution: Fixed > Conduct Apache NiFi 2.0.0-M3 Release > > > Key: NIFI-13219 > URL: https://issues.apache.org/jira/browse/NIFI-13219 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13256) Python WriteHelloWorld Example has Incorrect Attributes
David Handermann created NIFI-13256: --- Summary: Python WriteHelloWorld Example has Incorrect Attributes Key: NIFI-13256 URL: https://issues.apache.org/jira/browse/NIFI-13256 Project: Apache NiFi Issue Type: Bug Components: Documentation Website Affects Versions: 2.0.0-M2 Reporter: David Handermann Assignee: David Handermann The Python Developer Guide includes an example WriteHelloWorld Processor which defines a set instead of a dictionary for FlowFile attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13236) Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13236:
Affects Version/s: 2.0.0-M2
Status: Patch Available (was: Open)
> Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
> -
>
> Key: NIFI-13236
> URL: https://issues.apache.org/jira/browse/NIFI-13236
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 2.0.0-M2
>Reporter: Matt Gilman
>Assignee: David Handermann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When attempting to view or download content the flowfile's filename (from the
> filename attribute) is used as the proposed downloaded filename. These
> endpoints support gzip encoding. If the filename contains characters are
> invalid VCHAR based on RFC9110, the endpoint fails with a connection error.
> The log contains the following exception.
>
> {noformat}
> 2024-05-14 14:52:40,290 ERROR [NiFi Web Server-138]
> o.g.j.server.ServerRuntime$Responder An I/O error has occurred while writing
> a response message entity to the container output stream.
> org.glassfish.jersey.server.internal.process.MappableException:
> java.io.IOException:
> org.eclipse.jetty.http2.hpack.HpackException$SessionException: Could not
> hpack encode HTTP/2.0{s=200,h=11,cl=-1}
> at
> org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
> at
> org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
> at
> org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:678)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:387)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:377)
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:242)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
> at
> org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)
> at
> org.springframework.security.web.FilterChainProxy.lambda$doFilterInternal$3(FilterChainProxy.java:231)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:365)
> at
> org.springframework.security.web.access.intercept.AuthorizationFilter.doFilter(AuthorizationFilter.java:100)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:120)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.apache.nifi.web.security.log.AuthenticationUserFilter.doFilterInternal(AuthenticationUserFilter.java:57)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
>
[jira] [Updated] (NIFI-13236) Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13236:
Summary: Downloading Content with Non-ASCII Filenames Cause Exceptions with
HTTP/2 (was: Issue when viewing and downloading content)
> Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
> -
>
> Key: NIFI-13236
> URL: https://issues.apache.org/jira/browse/NIFI-13236
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Matt Gilman
>Assignee: David Handermann
>Priority: Major
>
> When attempting to view or download content the flowfile's filename (from the
> filename attribute) is used as the proposed downloaded filename. These
> endpoints support gzip encoding. If the filename contains characters are
> invalid VCHAR based on RFC9110, the endpoint fails with a connection error.
> The log contains the following exception.
>
> {noformat}
> 2024-05-14 14:52:40,290 ERROR [NiFi Web Server-138]
> o.g.j.server.ServerRuntime$Responder An I/O error has occurred while writing
> a response message entity to the container output stream.
> org.glassfish.jersey.server.internal.process.MappableException:
> java.io.IOException:
> org.eclipse.jetty.http2.hpack.HpackException$SessionException: Could not
> hpack encode HTTP/2.0{s=200,h=11,cl=-1}
> at
> org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
> at
> org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
> at
> org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:678)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:387)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:377)
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:242)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
> at
> org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)
> at
> org.springframework.security.web.FilterChainProxy.lambda$doFilterInternal$3(FilterChainProxy.java:231)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:365)
> at
> org.springframework.security.web.access.intercept.AuthorizationFilter.doFilter(AuthorizationFilter.java:100)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:120)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.apache.nifi.web.security.log.AuthenticationUserFilter.doFilterInternal(AuthenticationUserFilter.java:57)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
>
[jira] [Updated] (NIFI-12896) Add Endpoint Override Property to PutSNS
[ https://issues.apache.org/jira/browse/NIFI-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12896: Fix Version/s: 1.27.0 > Add Endpoint Override Property to PutSNS > > > Key: NIFI-12896 > URL: https://issues.apache.org/jira/browse/NIFI-12896 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sue Kim >Assignee: Sue Kim >Priority: Minor > Fix For: 1.27.0, 2.0.0-M4 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Request for PutSNS processor to have an endpoint override property similar to > Get/PutSQS processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12669) EvaluateXQuery processor incorrectly encodes result attributes
[
https://issues.apache.org/jira/browse/NIFI-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846695#comment-17846695
]
David Handermann commented on NIFI-12669:
-
[~mattyb149] I pushed an update to the support branch, correct to the
ByteArrayOutputStream.toString() method. The signature that takes a Charset was
added in Java 10, so the change requires using the String name of the character
set instead.
> EvaluateXQuery processor incorrectly encodes result attributes
> --
>
> Key: NIFI-12669
> URL: https://issues.apache.org/jira/browse/NIFI-12669
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Extensions
> Environment: JVM with non-UTF-8 default encoding (e.g. default
> Windows installation)
>Reporter: René Zeidler
>Assignee: Jim Steinebrey
>Priority: Major
> Labels: encoding, utf8, windows, xml
> Fix For: 1.27.0, 2.0.0-M4
>
> Attachments: EvaluateXQuery_Encoding_Bug.json,
> image-2024-01-25-10-24-17-005.png, image-2024-01-25-10-31-35-200.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Environment
> This issue affects environments where the JVM default encoding is not
> {{{}UTF-8{}}}. Standard Java installations on Windows are affected, as they
> usually use the default encoding {{{}windows-1252{}}}. To reproduce the issue
> on Linux, change the default encoding to {{windows-1252}} by adding the
> following line to your {{{}bootstrap.conf{}}}:
> {quote}{{java.arg.21=-Dfile.encoding=windows-1252}}
> {quote}
> h2. Summary
> The EvaluateXQuery incorrectly encodes result values when storing them in
> attributes. This causes non-ASCII characters to be garbled.
> Example:
> !image-2024-01-25-10-24-17-005.png!
> h2. Steps to reproduce
> # Make sure NiFi runs with a non-UTF-8 default encoding, see "Environment"
> # Create a GenerateFlowFile processor with the following content:
> {quote}{{}}
> {{}}
> {{ This text contains non-ASCII characters: ÄÖÜäöüßéèóò}}
> {{}}
> {quote}
> # Connect the processor to an EvaluateXQuery processor.
> Set the {{Destination}} to {{{}flowfile-attribute{}}}.
> Create a custom property {{myData}} with value {{{}string(/myRoot/myData){}}}.
> # Connect the outputs of the EvaluateXQuery processor to funnels to be able
> to observe the result in the queue.
> # Start the EvaluateXQuery processor and run the GenerateFlowFile processor
> once.
> The flow should look similar to this:
> !image-2024-01-25-10-31-35-200.png!
> I also attached a JSON export of the example flow.
> # Observe the attributes of the resulting FlowFile in the queue.
> h3. Expected Result
> The FlowFile should contain an attribute {{myData}} with the value {{{}"This
> text contains non-ASCII characters: ÄÖÜäöüßéèóò"{}}}.
> h3. Actual Result
> The attribute has the value "This text contains non-ASCII characters:
> ÄÖÜäöüßéèóò".
> h2. Root Cause Analysis
> EvaluateXQuery uses the method
> [{{formatItem}}|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L368-L372]
> to write the query result to an attribute. This method calls
> {{{}ByteArrayOutputStream{}}}'s
> [toString|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/ByteArrayOutputStream.html#toString()]
> method without an encoding argument, which then defaults to the default
> charset of the environment. Bytes are always written to this output stream
> using UTF-8
> ([.getBytes(StandardCharsets.UTF8)|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L397]).
> When the default charset is not UTF-8, this results in UTF-8 bytes to be
> interpreted in a different encoding when converting to a string, resulting in
> garbled text (see above).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12669) EvaluateXQuery processor incorrectly encodes result attributes
[
https://issues.apache.org/jira/browse/NIFI-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846695#comment-17846695
]
David Handermann edited comment on NIFI-12669 at 5/15/24 3:59 PM:
--
[~mattyb149] I pushed an update to the support branch, correcting the
ByteArrayOutputStream.toString() method. The signature that takes a Charset was
added in Java 10, so the change requires using the String name of the character
set instead.
was (Author: exceptionfactory):
[~mattyb149] I pushed an update to the support branch, correct to the
ByteArrayOutputStream.toString() method. The signature that takes a Charset was
added in Java 10, so the change requires using the String name of the character
set instead.
> EvaluateXQuery processor incorrectly encodes result attributes
> --
>
> Key: NIFI-12669
> URL: https://issues.apache.org/jira/browse/NIFI-12669
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Extensions
> Environment: JVM with non-UTF-8 default encoding (e.g. default
> Windows installation)
>Reporter: René Zeidler
>Assignee: Jim Steinebrey
>Priority: Major
> Labels: encoding, utf8, windows, xml
> Fix For: 1.27.0, 2.0.0-M4
>
> Attachments: EvaluateXQuery_Encoding_Bug.json,
> image-2024-01-25-10-24-17-005.png, image-2024-01-25-10-31-35-200.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Environment
> This issue affects environments where the JVM default encoding is not
> {{{}UTF-8{}}}. Standard Java installations on Windows are affected, as they
> usually use the default encoding {{{}windows-1252{}}}. To reproduce the issue
> on Linux, change the default encoding to {{windows-1252}} by adding the
> following line to your {{{}bootstrap.conf{}}}:
> {quote}{{java.arg.21=-Dfile.encoding=windows-1252}}
> {quote}
> h2. Summary
> The EvaluateXQuery incorrectly encodes result values when storing them in
> attributes. This causes non-ASCII characters to be garbled.
> Example:
> !image-2024-01-25-10-24-17-005.png!
> h2. Steps to reproduce
> # Make sure NiFi runs with a non-UTF-8 default encoding, see "Environment"
> # Create a GenerateFlowFile processor with the following content:
> {quote}{{}}
> {{}}
> {{ This text contains non-ASCII characters: ÄÖÜäöüßéèóò}}
> {{}}
> {quote}
> # Connect the processor to an EvaluateXQuery processor.
> Set the {{Destination}} to {{{}flowfile-attribute{}}}.
> Create a custom property {{myData}} with value {{{}string(/myRoot/myData){}}}.
> # Connect the outputs of the EvaluateXQuery processor to funnels to be able
> to observe the result in the queue.
> # Start the EvaluateXQuery processor and run the GenerateFlowFile processor
> once.
> The flow should look similar to this:
> !image-2024-01-25-10-31-35-200.png!
> I also attached a JSON export of the example flow.
> # Observe the attributes of the resulting FlowFile in the queue.
> h3. Expected Result
> The FlowFile should contain an attribute {{myData}} with the value {{{}"This
> text contains non-ASCII characters: ÄÖÜäöüßéèóò"{}}}.
> h3. Actual Result
> The attribute has the value "This text contains non-ASCII characters:
> ÄÖÜäöüßéèóò".
> h2. Root Cause Analysis
> EvaluateXQuery uses the method
> [{{formatItem}}|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L368-L372]
> to write the query result to an attribute. This method calls
> {{{}ByteArrayOutputStream{}}}'s
> [toString|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/ByteArrayOutputStream.html#toString()]
> method without an encoding argument, which then defaults to the default
> charset of the environment. Bytes are always written to this output stream
> using UTF-8
> ([.getBytes(StandardCharsets.UTF8)|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L397]).
> When the default charset is not UTF-8, this results in UTF-8 bytes to be
> interpreted in a different encoding when converting to a string, resulting in
> garbled text (see above).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13228) Jolt Transform UI uses incorrect property names
[ https://issues.apache.org/jira/browse/NIFI-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13228: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Jolt Transform UI uses incorrect property names > --- > > Key: NIFI-13228 > URL: https://issues.apache.org/jira/browse/NIFI-13228 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M2 >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > NIFI-12554 introducing a breaking change with the property names used by > JoltTransformJSON. The existing custom UI saves the transform and > specification into properties under the previous name. As a result, the > values are stored in dynamic properties. This custom UI needs to be updated > to leverage the new/updated Property names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13232) Add REST API Resource for Authentication Configuration
[ https://issues.apache.org/jira/browse/NIFI-13232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13232: Status: Patch Available (was: In Progress) > Add REST API Resource for Authentication Configuration > -- > > Key: NIFI-13232 > URL: https://issues.apache.org/jira/browse/NIFI-13232 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The NiFi user interface applications include Servlet Filters to handle Login > and Logout redirection based on the configured authentication strategy. > Rather than continuing to maintain these filters, a new REST API resource > should be created to provide login and logout URLs based on application > configuration. The response should also indicate whether the system supports > login and logout operations so that the user interface can present the > appropriate forms and links according to the current system configuration. > Implementing this new REST API should support the removal of the Login and > Logout filters from the new user interface, simplifying the build and > deployment process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13236) Issue when viewing and downloading content
[
https://issues.apache.org/jira/browse/NIFI-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann reassigned NIFI-13236:
---
Assignee: David Handermann
> Issue when viewing and downloading content
> --
>
> Key: NIFI-13236
> URL: https://issues.apache.org/jira/browse/NIFI-13236
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Matt Gilman
>Assignee: David Handermann
>Priority: Major
>
> When attempting to view or download content the flowfile's filename (from the
> filename attribute) is used as the proposed downloaded filename. These
> endpoints support gzip encoding. If the filename contains characters are
> invalid VCHAR based on RFC9110, the endpoint fails with a connection error.
> The log contains the following exception.
>
> {noformat}
> 2024-05-14 14:52:40,290 ERROR [NiFi Web Server-138]
> o.g.j.server.ServerRuntime$Responder An I/O error has occurred while writing
> a response message entity to the container output stream.
> org.glassfish.jersey.server.internal.process.MappableException:
> java.io.IOException:
> org.eclipse.jetty.http2.hpack.HpackException$SessionException: Could not
> hpack encode HTTP/2.0{s=200,h=11,cl=-1}
> at
> org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
> at
> org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
> at
> org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:678)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:387)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:377)
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:242)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
> at
> org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)
> at
> org.springframework.security.web.FilterChainProxy.lambda$doFilterInternal$3(FilterChainProxy.java:231)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:365)
> at
> org.springframework.security.web.access.intercept.AuthorizationFilter.doFilter(AuthorizationFilter.java:100)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:120)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.apache.nifi.web.security.log.AuthenticationUserFilter.doFilterInternal(AuthenticationUserFilter.java:57)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:100)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
>
[jira] [Resolved] (NIFI-12896) Add Endpoint Override Property to PutSNS
[ https://issues.apache.org/jira/browse/NIFI-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12896. - Fix Version/s: 2.0.0-M4 Resolution: Fixed > Add Endpoint Override Property to PutSNS > > > Key: NIFI-12896 > URL: https://issues.apache.org/jira/browse/NIFI-12896 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sue Kim >Assignee: Sue Kim >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Request for PutSNS processor to have an endpoint override property similar to > Get/PutSQS processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12896) Add Endpoint Override Property to PutSNS
[ https://issues.apache.org/jira/browse/NIFI-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12896: Summary: Add Endpoint Override Property to PutSNS (was: PutSNS Endpoint Override) > Add Endpoint Override Property to PutSNS > > > Key: NIFI-12896 > URL: https://issues.apache.org/jira/browse/NIFI-12896 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Sue Kim >Assignee: Sue Kim >Priority: Minor > Time Spent: 2h 10m > Remaining Estimate: 0h > > Request for PutSNS processor to have an endpoint override property similar to > Get/PutSQS processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12896) Add Endpoint Override Property to PutSNS
[ https://issues.apache.org/jira/browse/NIFI-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12896: Issue Type: Improvement (was: New Feature) > Add Endpoint Override Property to PutSNS > > > Key: NIFI-12896 > URL: https://issues.apache.org/jira/browse/NIFI-12896 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sue Kim >Assignee: Sue Kim >Priority: Minor > Time Spent: 2h 10m > Remaining Estimate: 0h > > Request for PutSNS processor to have an endpoint override property similar to > Get/PutSQS processors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13225) Replace the deprecated methods/classes/enums in JwtService with API suggestions
[
https://issues.apache.org/jira/browse/NIFI-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13225:
Fix Version/s: 2.0.0-M4
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace the deprecated methods/classes/enums in JwtService with API
> suggestions
> ---
>
> Key: NIFI-13225
> URL: https://issues.apache.org/jira/browse/NIFI-13225
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> These are the warnings seen from a build
> {code:java}
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[47,25]
> [deprecation] SignatureAlgorithm in io.jsonwebtoken has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[47,66]
> [deprecation] SignatureAlgorithm in io.jsonwebtoken has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[68,39]
> [deprecation] getBody() in Jwt has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[73,39]
> [deprecation] getBody() in Jwt has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[76,22]
> [deprecation] getBody() in Jwt has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[87,59]
> [deprecation] SigningKeyResolverAdapter in io.jsonwebtoken has been
> deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[87,32]
> [deprecation] setSigningKeyResolver(SigningKeyResolver) in JwtParserBuilder
> has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[103,22]
> [deprecation] parseClaimsJws(CharSequence) in JwtParser has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[104,73]
> [deprecation] SignatureException in io.jsonwebtoken has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[155,33]
> [deprecation] setSubject(String) in ClaimsMutator has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[156,20]
> [deprecation] setIssuer(String) in ClaimsMutator has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[157,20]
> [deprecation] setAudience(String) in ClaimsMutator has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[160,20]
> [deprecation] setIssuedAt(Date) in ClaimsMutator has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[161,20]
> [deprecation] setExpiration(Date) in ClaimsMutator has been deprecated
> [WARNING]
> nifi-registry/nifi-registry-core/nifi-registry-web-api/src/main/java/org/apache/nifi/registry/web/security/authentication/jwt/JwtService.java:[162,20]
> [deprecation] signWith(SignatureAlgorithm,byte[]) in JwtBuilder has been
> deprecated
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-13235) Import from registry to a PG without read permissions causes NPE
[
https://issues.apache.org/jira/browse/NIFI-13235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-13235.
-
Fix Version/s: 2.0.0-M4
Assignee: Bryan Bende
Resolution: Fixed
> Import from registry to a PG without read permissions causes NPE
>
>
> Key: NIFI-13235
> URL: https://issues.apache.org/jira/browse/NIFI-13235
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 2.0.0-M2
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 2.0.0-M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If you are inside a PG where you have WRITE permissions, but not READ
> permissions, and you import a new PG from a registry client, it results in an
> unexpected error page and an NPE in the logs:
> {code:java}
> 2024-05-14 13:41:46,946 ERROR [NiFi Web Server-139]
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
> java.lang.NullPointerException: Cannot invoke
> "org.apache.nifi.web.api.dto.ProcessGroupDTO.getId()" because the return
> value of "org.apache.nifi.web.api.entity.ProcessGroupEntity.getComponent()"
> is null. Returning Internal Server Error response.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.nifi.web.api.dto.ProcessGroupDTO.getId()" because the return
> value of "org.apache.nifi.web.api.entity.ProcessGroupEntity.getComponent()"
> is null
> at
> org.apache.nifi.web.api.ProcessGroupResource.lambda$createProcessGroup$18(ProcessGroupResource.java:1016)
> at
> org.apache.nifi.web.api.ApplicationResource.withWriteLock(ApplicationResource.java:691)
> at
> org.apache.nifi.web.api.ProcessGroupResource.createProcessGroup(ProcessGroupResource.java:988)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13238) Checkstyle - rules for whitespace
[ https://issues.apache.org/jira/browse/NIFI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13238: Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Checkstyle - rules for whitespace > - > > Key: NIFI-13238 > URL: https://issues.apache.org/jira/browse/NIFI-13238 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > Adding the following rules: > * WhitespaceAfter > * NoWhitespaceAfter > * NoWhitespaceBefore > * WhitespaceAround -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13232) Add REST API Resource for Authentication Configuration
David Handermann created NIFI-13232: --- Summary: Add REST API Resource for Authentication Configuration Key: NIFI-13232 URL: https://issues.apache.org/jira/browse/NIFI-13232 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: David Handermann Assignee: David Handermann The NiFi user interface applications include Servlet Filters to handle Login and Logout redirection based on the configured authentication strategy. Rather than continuing to maintain these filters, a new REST API resource should be created to provide login and logout URLs based on application configuration. The response should also indicate whether the system supports login and logout operations so that the user interface can present the appropriate forms and links according to the current system configuration. Implementing this new REST API should support the removal of the Login and Logout filters from the new user interface, simplifying the build and deployment process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12669) EvaluateXQuery processor incorrectly encodes result attributes
[
https://issues.apache.org/jira/browse/NIFI-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12669:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> EvaluateXQuery processor incorrectly encodes result attributes
> --
>
> Key: NIFI-12669
> URL: https://issues.apache.org/jira/browse/NIFI-12669
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Extensions
> Environment: JVM with non-UTF-8 default encoding (e.g. default
> Windows installation)
>Reporter: René Zeidler
>Assignee: Jim Steinebrey
>Priority: Major
> Labels: encoding, utf8, windows, xml
> Fix For: 1.27.0, 2.0.0
>
> Attachments: EvaluateXQuery_Encoding_Bug.json,
> image-2024-01-25-10-24-17-005.png, image-2024-01-25-10-31-35-200.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Environment
> This issue affects environments where the JVM default encoding is not
> {{{}UTF-8{}}}. Standard Java installations on Windows are affected, as they
> usually use the default encoding {{{}windows-1252{}}}. To reproduce the issue
> on Linux, change the default encoding to {{windows-1252}} by adding the
> following line to your {{{}bootstrap.conf{}}}:
> {quote}{{java.arg.21=-Dfile.encoding=windows-1252}}
> {quote}
> h2. Summary
> The EvaluateXQuery incorrectly encodes result values when storing them in
> attributes. This causes non-ASCII characters to be garbled.
> Example:
> !image-2024-01-25-10-24-17-005.png!
> h2. Steps to reproduce
> # Make sure NiFi runs with a non-UTF-8 default encoding, see "Environment"
> # Create a GenerateFlowFile processor with the following content:
> {quote}{{}}
> {{}}
> {{ This text contains non-ASCII characters: ÄÖÜäöüßéèóò}}
> {{}}
> {quote}
> # Connect the processor to an EvaluateXQuery processor.
> Set the {{Destination}} to {{{}flowfile-attribute{}}}.
> Create a custom property {{myData}} with value {{{}string(/myRoot/myData){}}}.
> # Connect the outputs of the EvaluateXQuery processor to funnels to be able
> to observe the result in the queue.
> # Start the EvaluateXQuery processor and run the GenerateFlowFile processor
> once.
> The flow should look similar to this:
> !image-2024-01-25-10-31-35-200.png!
> I also attached a JSON export of the example flow.
> # Observe the attributes of the resulting FlowFile in the queue.
> h3. Expected Result
> The FlowFile should contain an attribute {{myData}} with the value {{{}"This
> text contains non-ASCII characters: ÄÖÜäöüßéèóò"{}}}.
> h3. Actual Result
> The attribute has the value "This text contains non-ASCII characters:
> ÄÖÜäöüßéèóò".
> h2. Root Cause Analysis
> EvaluateXQuery uses the method
> [{{formatItem}}|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L368-L372]
> to write the query result to an attribute. This method calls
> {{{}ByteArrayOutputStream{}}}'s
> [toString|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/ByteArrayOutputStream.html#toString()]
> method without an encoding argument, which then defaults to the default
> charset of the environment. Bytes are always written to this output stream
> using UTF-8
> ([.getBytes(StandardCharsets.UTF8)|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L397]).
> When the default charset is not UTF-8, this results in UTF-8 bytes to be
> interpreted in a different encoding when converting to a string, resulting in
> garbled text (see above).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12669) EvaluateXQuery processor incorrectly encodes result attributes
[
https://issues.apache.org/jira/browse/NIFI-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12669:
Fix Version/s: 1.27.0
2.0.0
> EvaluateXQuery processor incorrectly encodes result attributes
> --
>
> Key: NIFI-12669
> URL: https://issues.apache.org/jira/browse/NIFI-12669
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Extensions
> Environment: JVM with non-UTF-8 default encoding (e.g. default
> Windows installation)
>Reporter: René Zeidler
>Assignee: Jim Steinebrey
>Priority: Major
> Labels: encoding, utf8, windows, xml
> Fix For: 1.27.0, 2.0.0
>
> Attachments: EvaluateXQuery_Encoding_Bug.json,
> image-2024-01-25-10-24-17-005.png, image-2024-01-25-10-31-35-200.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Environment
> This issue affects environments where the JVM default encoding is not
> {{{}UTF-8{}}}. Standard Java installations on Windows are affected, as they
> usually use the default encoding {{{}windows-1252{}}}. To reproduce the issue
> on Linux, change the default encoding to {{windows-1252}} by adding the
> following line to your {{{}bootstrap.conf{}}}:
> {quote}{{java.arg.21=-Dfile.encoding=windows-1252}}
> {quote}
> h2. Summary
> The EvaluateXQuery incorrectly encodes result values when storing them in
> attributes. This causes non-ASCII characters to be garbled.
> Example:
> !image-2024-01-25-10-24-17-005.png!
> h2. Steps to reproduce
> # Make sure NiFi runs with a non-UTF-8 default encoding, see "Environment"
> # Create a GenerateFlowFile processor with the following content:
> {quote}{{}}
> {{}}
> {{ This text contains non-ASCII characters: ÄÖÜäöüßéèóò}}
> {{}}
> {quote}
> # Connect the processor to an EvaluateXQuery processor.
> Set the {{Destination}} to {{{}flowfile-attribute{}}}.
> Create a custom property {{myData}} with value {{{}string(/myRoot/myData){}}}.
> # Connect the outputs of the EvaluateXQuery processor to funnels to be able
> to observe the result in the queue.
> # Start the EvaluateXQuery processor and run the GenerateFlowFile processor
> once.
> The flow should look similar to this:
> !image-2024-01-25-10-31-35-200.png!
> I also attached a JSON export of the example flow.
> # Observe the attributes of the resulting FlowFile in the queue.
> h3. Expected Result
> The FlowFile should contain an attribute {{myData}} with the value {{{}"This
> text contains non-ASCII characters: ÄÖÜäöüßéèóò"{}}}.
> h3. Actual Result
> The attribute has the value "This text contains non-ASCII characters:
> ÄÖÜäöüßéèóò".
> h2. Root Cause Analysis
> EvaluateXQuery uses the method
> [{{formatItem}}|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L368-L372]
> to write the query result to an attribute. This method calls
> {{{}ByteArrayOutputStream{}}}'s
> [toString|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/ByteArrayOutputStream.html#toString()]
> method without an encoding argument, which then defaults to the default
> charset of the environment. Bytes are always written to this output stream
> using UTF-8
> ([.getBytes(StandardCharsets.UTF8)|https://github.com/apache/nifi/blob/2e3f83eb54cbc040b5a1da5bce9a74a558f08ea4/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/EvaluateXQuery.java#L397]).
> When the default charset is not UTF-8, this results in UTF-8 bytes to be
> interpreted in a different encoding when converting to a string, resulting in
> garbled text (see above).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13144) Improve dependency-update detection configuration and bump various detected dependency versions
[
https://issues.apache.org/jira/browse/NIFI-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13144:
Issue Type: Improvement (was: Task)
> Improve dependency-update detection configuration and bump various detected
> dependency versions
> ---
>
> Key: NIFI-13144
> URL: https://issues.apache.org/jira/browse/NIFI-13144
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> com.puppycrawl.tools:checkstyle ... 10.15.0 -> 10.16.0
> software.amazon.awssdk:xray ... 2.25.40 -> 2.25.45
> com.amazonaws:aws-java-sdk-keyspaces 1.12.710 -> 1.12.715
> com.azure:azure-sdk-bom 1.2.21 -> 1.2.23
> com.google.cloud:libraries-bom ... 26.37.0 -> 26.38.0
> net.bytebuddy:byte-buddy .. 1.14.12 -> 1.14.14
> org.checkerframework:checker-qual ... 3.37.0 -> 3.43.0
> org.eclipse.jdt:ecj . 3.33.0 -> 3.37.0
> com.microsoft.azure:msal4j .. 1.14.3 -> 1.15.0
> com.google.guava:guava .. 33.1.0-jre -> 33.2.0-jre
> com.ibm.icu:icu4j ... 74.2 -> 75.1
> org.opensaml:opensaml-* 4.3.1 -> 4.3.2
> org.apache.sshd:sshd-* ... 2.12.0 -> 2.12.1
> com.nimbusds:oauth2-oidc-sdk ... 9.43.3 -> 9.43.4
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12914) Upgrade follow-redirects library to 1.15.6
[ https://issues.apache.org/jira/browse/NIFI-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12914: Issue Type: Improvement (was: Task) > Upgrade follow-redirects library to 1.15.6 > -- > > Key: NIFI-12914 > URL: https://issues.apache.org/jira/browse/NIFI-12914 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Priority: Minor > Fix For: 2.0.0-M3 > > > Bump follow-redirects from 1.15.5 to 1.15.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12853) Refactor FlowFilePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12853: Issue Type: Improvement (was: Task) > Refactor FlowFilePrioritizer using updated Java APIs > > > Key: NIFI-12853 > URL: https://issues.apache.org/jira/browse/NIFI-12853 > Project: Apache NiFi > Issue Type: Improvement >Reporter: endzeit >Assignee: endzeit >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The FlowFilePrioritizer implementations and test contain some boilerplate / > duplication that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12914) Upgrade follow-redirects library to 1.15.6
[ https://issues.apache.org/jira/browse/NIFI-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12914: Priority: Minor (was: Major) > Upgrade follow-redirects library to 1.15.6 > -- > > Key: NIFI-12914 > URL: https://issues.apache.org/jira/browse/NIFI-12914 > Project: Apache NiFi > Issue Type: Task > Components: Core UI >Reporter: Matt Gilman >Priority: Minor > Fix For: 2.0.0-M3 > > > Bump follow-redirects from 1.15.5 to 1.15.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12914) Upgrade follow-redirects library to 1.15.6
[ https://issues.apache.org/jira/browse/NIFI-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12914: Summary: Upgrade follow-redirects library to 1.15.6 (was: Dependabot: follow-redirects) > Upgrade follow-redirects library to 1.15.6 > -- > > Key: NIFI-12914 > URL: https://issues.apache.org/jira/browse/NIFI-12914 > Project: Apache NiFi > Issue Type: Task > Components: Core UI >Reporter: Matt Gilman >Priority: Major > Fix For: 2.0.0-M3 > > > Bump follow-redirects from 1.15.5 to 1.15.6 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13215) Update AWS, OpenTelemetry, latest dependency scan findings
[ https://issues.apache.org/jira/browse/NIFI-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13215: Priority: Minor (was: Major) > Update AWS, OpenTelemetry, latest dependency scan findings > -- > > Key: NIFI-13215 > URL: https://issues.apache.org/jira/browse/NIFI-13215 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13215) Update AWS, OpenTelemetry, latest dependency scan findings
[ https://issues.apache.org/jira/browse/NIFI-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13215: Issue Type: Improvement (was: Task) > Update AWS, OpenTelemetry, latest dependency scan findings > -- > > Key: NIFI-13215 > URL: https://issues.apache.org/jira/browse/NIFI-13215 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12853) Refactor FlowFilePrioritizer using updated Java APIs
[ https://issues.apache.org/jira/browse/NIFI-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12853: Priority: Minor (was: Major) > Refactor FlowFilePrioritizer using updated Java APIs > > > Key: NIFI-12853 > URL: https://issues.apache.org/jira/browse/NIFI-12853 > Project: Apache NiFi > Issue Type: Task >Reporter: endzeit >Assignee: endzeit >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The FlowFilePrioritizer implementations and test contain some boilerplate / > duplication that can be reduced by using updated Java APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13113) Upgrade Iceberg from 1.5.0 to 1.5.2
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13113: Summary: Upgrade Iceberg from 1.5.0 to 1.5.2 (was: upgrade Iceberg from 1.5.0 to 1.5.2) > Upgrade Iceberg from 1.5.0 to 1.5.2 > --- > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sean Sullivan >Assignee: Joe Witt >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13193) Update maven plugins to latest and require minimum of Apache Maven 3.9.6
[
https://issues.apache.org/jira/browse/NIFI-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13193:
Issue Type: Improvement (was: Task)
> Update maven plugins to latest and require minimum of Apache Maven 3.9.6
>
>
> Key: NIFI-13193
> URL: https://issues.apache.org/jira/browse/NIFI-13193
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Joe Witt
>Assignee: Joe Witt
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Apache Maven 3.8.5 is more than two years old already and many plugin updates
> suggest they require at least that. Bumping versions found during plugin
> update scanning and bumping to that minimum maven version.
> {noformat}
> Update Maven Plugins
> org.codehaus.mojo:exec-maven-plugin 3.1.0 -> 3.2.0
> maven-clean-plugin . 3.3.1 -> 3.3.2
> com.github.eirslett:frontend-maven-plugin 1.14.2 -> 1.15.0
> com.coderplus.maven.plugins:copy-rename-maven-plugin . 1.0 -> 1.0.1
> org.codehaus.mojo:license-maven-plugin . 2.2.0 -> 2.4.0
> org.asciidoctor:asciidoctor-maven-plugin ... 2.2.4 -> 2.2.6 (or 3.0.0
> if we want to require maven 3.8.5)
> com.googlecode.maven-download-plugin:download-maven-plugin 1.7.1 -> 1.9.0
> com.github.spotbugs:spotbugs-maven-plugin .. 4.7.3.5 -> 4.8.5.0
> maven-jar-plugin ... 3.3.0 -> 3.4.1
> org.codehaus.mojo:jaxb2-maven-plugin ... 3.1.0 -> 3.2.0
> org.patrodyne.jvnet:hisrc-higherjaxb40-maven-plugin 2.1.1 -> 2.2.0 (require
> maven 3.8.4)
> org.jacoco:jacoco-maven-plugin ... 0.8.11 -> 0.8.12
> io.swagger.core.v3:swagger-maven-plugin-jakarta .. 2.2.20 -> 2.2.21
> io.swagger.codegen.v3:swagger-codegen-maven-plugin 3.0.52 -> 3.0.55
> {noformat}
> Not worth doing now as it causes some failure and we need to run that down.
> io.fabric8:docker-maven-plugin ... 0.43.4 -> 0.44.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13178) Upgrade Apache Mina, UnboundID Ldap, oktthp-digest, reactor-netty, jetbrains-annotations, reactor-core
[ https://issues.apache.org/jira/browse/NIFI-13178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13178: Issue Type: Improvement (was: Task) > Upgrade Apache Mina, UnboundID Ldap, oktthp-digest, reactor-netty, > jetbrains-annotations, reactor-core > -- > > Key: NIFI-13178 > URL: https://issues.apache.org/jira/browse/NIFI-13178 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13179) Bump oauth-oidc-sdk 9.43.4 to 11.10.1
[ https://issues.apache.org/jira/browse/NIFI-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13179: Issue Type: Improvement (was: Task) > Bump oauth-oidc-sdk 9.43.4 to 11.10.1 > - > > Key: NIFI-13179 > URL: https://issues.apache.org/jira/browse/NIFI-13179 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > oauth-oidc-sdk 9.43.4 (sep 22) to 11.10.1 (Mar 24) > Seems relatively safe. > https://bitbucket.org/connect2id/oauth-2.0-sdk-with-openid-connect-extensions/src/master/CHANGELOG.txt. > Read all release notes and verified noted dependency changes are already in > our build anyway. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13179) Upgrade oauth-oidc-sdk 9.43.4 to 11.10.1
[ https://issues.apache.org/jira/browse/NIFI-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13179: Summary: Upgrade oauth-oidc-sdk 9.43.4 to 11.10.1 (was: Bump oauth-oidc-sdk 9.43.4 to 11.10.1) > Upgrade oauth-oidc-sdk 9.43.4 to 11.10.1 > > > Key: NIFI-13179 > URL: https://issues.apache.org/jira/browse/NIFI-13179 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > oauth-oidc-sdk 9.43.4 (sep 22) to 11.10.1 (Mar 24) > Seems relatively safe. > https://bitbucket.org/connect2id/oauth-2.0-sdk-with-openid-connect-extensions/src/master/CHANGELOG.txt. > Read all release notes and verified noted dependency changes are already in > our build anyway. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13113) upgrade Iceberg from 1.5.0 to 1.5.2
[ https://issues.apache.org/jira/browse/NIFI-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13113: Issue Type: Improvement (was: Task) > upgrade Iceberg from 1.5.0 to 1.5.2 > --- > > Key: NIFI-13113 > URL: https://issues.apache.org/jira/browse/NIFI-13113 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sean Sullivan >Assignee: Joe Witt >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > > Iceberg 1.5.2 > > [https://iceberg.apache.org/releases/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13007) Remove Apache Solr Components
[ https://issues.apache.org/jira/browse/NIFI-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13007: Summary: Remove Apache Solr Components (was: Remove Solr Components in 2x line) > Remove Apache Solr Components > - > > Key: NIFI-13007 > URL: https://issues.apache.org/jira/browse/NIFI-13007 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > In NIFI-12998 it was found that with basic dependency hygiene our Solr > components cant even build now. And it turns out they already dont work at > runtime. > In NIFi-13006 we deprecate and in this JIRA we remove. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12906) Upgrade ZooKeeper to 3.9.2
[ https://issues.apache.org/jira/browse/NIFI-12906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12906: Issue Type: Improvement (was: Task) > Upgrade ZooKeeper to 3.9.2 > -- > > Key: NIFI-12906 > URL: https://issues.apache.org/jira/browse/NIFI-12906 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.26.0, 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12907) Update to Groovy 4.0.20
[ https://issues.apache.org/jira/browse/NIFI-12907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12907: Issue Type: Improvement (was: Task) > Update to Groovy 4.0.20 > --- > > Key: NIFI-12907 > URL: https://issues.apache.org/jira/browse/NIFI-12907 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13228) Jolt Transform UI uses incorrect property names
[ https://issues.apache.org/jira/browse/NIFI-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13228: Affects Version/s: 2.0.0-M2 > Jolt Transform UI uses incorrect property names > --- > > Key: NIFI-13228 > URL: https://issues.apache.org/jira/browse/NIFI-13228 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 2.0.0-M2 >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NIFI-12554 introducing a breaking change with the property names used by > JoltTransformJSON. The existing custom UI saves the transform and > specification into properties under the previous name. As a result, the > values are stored in dynamic properties. This custom UI needs to be updated > to leverage the new/updated Property names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13224) Replace deprecated commons-compress IOUtils.toByteArray(InputStream) with commons-io IOUtils.toByteArray(InputStream)
[ https://issues.apache.org/jira/browse/NIFI-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13224: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace deprecated commons-compress IOUtils.toByteArray(InputStream) with > commons-io IOUtils.toByteArray(InputStream) > - > > Key: NIFI-13224 > URL: https://issues.apache.org/jira/browse/NIFI-13224 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > Changes should be made for files > # > nifi-extension-bundles/nifi-extension-utils/nifi-record-utils/nifi-avro-record-utils/src/main/java/org/apache/nifi/avro/AvroTypeUtil.java > # > nifi-extension-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service/src/test/java/org/apache/nifi/elasticsearch/integration/ElasticSearchClientService_IT.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13222) Replace deprecated commons-compress IOUtils.closeQuietly(Closeable) with commons-io IOUtils.closeQuietly(Closeable)
[
https://issues.apache.org/jira/browse/NIFI-13222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13222:
Fix Version/s: 2.0.0-M3
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace deprecated commons-compress IOUtils.closeQuietly(Closeable) with
> commons-io IOUtils.closeQuietly(Closeable)
> ---
>
> Key: NIFI-13222
> URL: https://issues.apache.org/jira/browse/NIFI-13222
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This change must be applied to
> {code:java}
> c2/c2-client-bundle/c2-client-service/src/main/java/org/apache/nifi/c2/client/service/operation/TransferDebugOperationHandler
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13169) Upgrade NiFi Registry to Flyway DB 10.latest
[ https://issues.apache.org/jira/browse/NIFI-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13169: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade NiFi Registry to Flyway DB 10.latest > > > Key: NIFI-13169 > URL: https://issues.apache.org/jira/browse/NIFI-13169 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13223) Replace commons-lang3 CharSequenceTranslator, AggregateTranslator, LookupTranslator and UnicodeUnpairedSurrogateRemover with suggested API replacements
[
https://issues.apache.org/jira/browse/NIFI-13223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13223:
Fix Version/s: 2.0.0-M3
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace commons-lang3 CharSequenceTranslator, AggregateTranslator,
> LookupTranslator and UnicodeUnpairedSurrogateRemover with suggested API
> replacements
> ---
>
> Key: NIFI-13223
> URL: https://issues.apache.org/jira/browse/NIFI-13223
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Changes must be applied to
> {code:java}
> nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/util/CharacterFilterUtils
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13169) Upgrade NiFi Registry to Flyway DB 10.12.0
[ https://issues.apache.org/jira/browse/NIFI-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13169: Issue Type: Improvement (was: Task) > Upgrade NiFi Registry to Flyway DB 10.12.0 > -- > > Key: NIFI-13169 > URL: https://issues.apache.org/jira/browse/NIFI-13169 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13169) Upgrade NiFi Registry to Flyway DB 10.12.0
[ https://issues.apache.org/jira/browse/NIFI-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13169: Summary: Upgrade NiFi Registry to Flyway DB 10.12.0 (was: Upgrade NiFi Registry to Flyway DB 10.latest) > Upgrade NiFi Registry to Flyway DB 10.12.0 > -- > > Key: NIFI-13169 > URL: https://issues.apache.org/jira/browse/NIFI-13169 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13220) Filter out buckets users don't have write access to from dropdown
[ https://issues.apache.org/jira/browse/NIFI-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13220: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Filter out buckets users don't have write access to from dropdown > - > > Key: NIFI-13220 > URL: https://issues.apache.org/jira/browse/NIFI-13220 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > When starting version control, buckets where the user does not have write > access to should not be available to select. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12916) Develop an ExecutePythonScript Processor
[ https://issues.apache.org/jira/browse/NIFI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12916: Fix Version/s: (was: 2.0.0-M3) > Develop an ExecutePythonScript Processor > > > Key: NIFI-12916 > URL: https://issues.apache.org/jira/browse/NIFI-12916 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 2.0.0-M2 >Reporter: Fredrick Eisele >Priority: Major > > Given the ability to create python processors in NiFi 2, and the presence of > ExecuteGroovyScript, development of an ExecutePythonScript processor seems > logical. > That said there will be differences due to differences between on the NiFi > Python and JVM support. > The first step is to outline what capabilities are or may be possible. > "The new native Python support in NiFi 2.0 provides a more streamlined API > for Processor implementation, as opposed to the full set of capabilities that > the Java Processor API provides. > This enables simplified Processor implementation, and streamlined > communication between Java and Python processes. > For that reason, a generic ExecutePythonScript would not provide all of the > same options as the generalized ExecuteGroovyScript." > Ref: > * > [https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-groovyx-bundle/nifi-groovyx-processors/src/main/java/org/apache/nifi/processors/groovyx] > * > [https://nifi.apache.org/documentation/nifi-2.0.0-M2/html/python-developer-guide.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13219) Conduct Apache NiFi 2.0.0-M3 Release
David Handermann created NIFI-13219: --- Summary: Conduct Apache NiFi 2.0.0-M3 Release Key: NIFI-13219 URL: https://issues.apache.org/jira/browse/NIFI-13219 Project: Apache NiFi Issue Type: Task Reporter: David Handermann Assignee: David Handermann Fix For: 2.0.0-M3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13127) Support branch selection for registry providers that offer branching
[ https://issues.apache.org/jira/browse/NIFI-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13127: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Support branch selection for registry providers that offer branching > > > Key: NIFI-13127 > URL: https://issues.apache.org/jira/browse/NIFI-13127 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > This is intended to be the UI portion of NIFI-13120. There is a Pull Request > available: [https://github.com/apache/nifi/pull/8726] > > Essentially what is needed is that the the registry client supports > branching, a new branch dropdown should be inserted between the registry > selection and the bucket selection. Changing the registry should reload the > branches, changing the branch should reload the buckets and so forth. > Impacted areas would be: > * Import from registry > * Start Version Control > * Change Version dialog - read only display of the branch > * Commit local changes dialog - read only display of the branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13216) Replace deprecated GzipUtils methods isCompressedFilename and getUncompressedFilename with the API suggested alternatives
[
https://issues.apache.org/jira/browse/NIFI-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13216:
Fix Version/s: 2.0.0-M3
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Replace deprecated GzipUtils methods isCompressedFilename and
> getUncompressedFilename with the API suggested alternatives
> -
>
> Key: NIFI-13216
> URL: https://issues.apache.org/jira/browse/NIFI-13216
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> These methods need to be changed in
> {code:java}
> c2/c2-client-bundle/c2-client-service/src/main/java/org/apache/nifi/c2/client/service/operation/TransferDebugOperationHandler.java
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13214) Replace use of deprecated org.apache.lucene.index.IndexReader document methods with API suggestion
[ https://issues.apache.org/jira/browse/NIFI-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13214: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace use of deprecated org.apache.lucene.index.IndexReader document > methods with API suggestion > -- > > Key: NIFI-13214 > URL: https://issues.apache.org/jira/browse/NIFI-13214 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > Files which are using the deprecated document methods > # > nifi-extension-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/lucene/DocsReader.java > # > nifi-extension-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/index/lucene/QueryTask.java > # > nifi-extension-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/index/lucene/LuceneEventIndex.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13185) Remove "integration tests" which are not maintained and require personal credentials to Cloud services
[ https://issues.apache.org/jira/browse/NIFI-13185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13185: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove "integration tests" which are not maintained and require personal > credentials to Cloud services > -- > > Key: NIFI-13185 > URL: https://issues.apache.org/jira/browse/NIFI-13185 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 10m > Remaining Estimate: 0h > > There is a rather large chunk of code and pom configuration sitting in our > codebase for tests which are never run or maintained. These are for cloud > services/integrations that are simply not exercised/maintained and are > therefore not useful. Of course having real tests to these systems is > valuable but unless they're run and maintained they're not. Meanwhile a ton > of excellent work has occurred to vet behaviors using things like test > containers and those are easily run by anyone with docker/etc.. > We should remove all these tests which dont get maintained and require > special permissions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13215) Update AWS, OpenTelemetry, latest dependency scan findings
[ https://issues.apache.org/jira/browse/NIFI-13215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13215: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Update AWS, OpenTelemetry, latest dependency scan findings > -- > > Key: NIFI-13215 > URL: https://issues.apache.org/jira/browse/NIFI-13215 > Project: Apache NiFi > Issue Type: Task >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13217) Update JavaDoc on core attributes unaffected by removeAttribute / removeAllAttributes
[
https://issues.apache.org/jira/browse/NIFI-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-13217.
-
Fix Version/s: 2.0.0-M3
Resolution: Fixed
> Update JavaDoc on core attributes unaffected by removeAttribute /
> removeAllAttributes
> -
>
> Key: NIFI-13217
> URL: https://issues.apache.org/jira/browse/NIFI-13217
> Project: Apache NiFi
> Issue Type: Task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> NIFI-13200 introduced a behavioral change to the {{standard}} implementation
> of {{ProcessSession}}.
> The existing JavaDoc of {{ProcessSession}} notes that {{removeAttribute}} and
> {{removeAllAttributes}} do not affect the core attribute {{uuid}}. A similar
> note should be added for the core attributes {{path}} and {{filename}} which
> are exempt as well now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13213) Add Validation for Swap File Names
[ https://issues.apache.org/jira/browse/NIFI-13213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13213: Status: Patch Available (was: Open) > Add Validation for Swap File Names > -- > > Key: NIFI-13213 > URL: https://issues.apache.org/jira/browse/NIFI-13213 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The FileSystemSwapManager supports persisting FlowFiles to disk in files > named according to the FlowFileQueue identifier. The identifier consists of a > UUID string, so file name generation should incorporate basic validation to > ensure expected behavior from calling components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13213) Add Validation for Swap File Names
David Handermann created NIFI-13213: --- Summary: Add Validation for Swap File Names Key: NIFI-13213 URL: https://issues.apache.org/jira/browse/NIFI-13213 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: David Handermann Assignee: David Handermann The FileSystemSwapManager supports persisting FlowFiles to disk in files named according to the FlowFileQueue identifier. The identifier consists of a UUID string, so file name generation should incorporate basic validation to ensure expected behavior from calling components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12317) REST API Rejects Keycloak OIDC Access Tokens with HTTP 401
[ https://issues.apache.org/jira/browse/NIFI-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12317: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > REST API Rejects Keycloak OIDC Access Tokens with HTTP 401 > -- > > Key: NIFI-12317 > URL: https://issues.apache.org/jira/browse/NIFI-12317 > Project: Apache NiFi > Issue Type: Improvement > Components: Security >Reporter: Anmol >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M3 > > > I have integrated Nifi with keycloak and NIfi UI is working fine. But if i am > hitting nifi-api with keycloak access token , nifi is giving 401 error. > > error: Unauthorized error="invalid_token", error_description="An error > occurred while attempting to decode the Jwt: Signed JWT rejected: Another > algorithm expected, or no matching key(s) found", > error_uri="https://tools.ietf.org/html/rfc6750#section-3.1; -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12550) Support OIDC Device Authorization Grant for API
[ https://issues.apache.org/jira/browse/NIFI-12550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12550: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Support OIDC Device Authorization Grant for API > --- > > Key: NIFI-12550 > URL: https://issues.apache.org/jira/browse/NIFI-12550 > Project: Apache NiFi > Issue Type: Improvement > Components: Security > Environment: NiFi with OIDC provider configured >Reporter: Igor Milavec >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M3 > > > Please add support for OIDC Device Authorization Grant. This is useful for > running scripts that access the NiFi API from the CLI. At this time the > options are: > # Copy __Secure-Authorization-Bearer cookie from the browser session: not > really a good practice, work and error prone > # Enable MTLS: painful for the users as the browser starts to frequently > challenge for the client cert and even if it worked fine, client certificate > management process is typically lagging behind OIDC identity management > # Use passwords: insecure and prohibited by policy > Having an API endpoint in the Access group that would allow the caller to > exchange OIDC id or refresh token for a NiFi session token would be perfect > for this use case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13210) Add Codecov Token to GitHub Actions
[
https://issues.apache.org/jira/browse/NIFI-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13210:
Status: Patch Available (was: In Progress)
> Add Codecov Token to GitHub Actions
> ---
>
> Key: NIFI-13210
> URL: https://issues.apache.org/jira/browse/NIFI-13210
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Codecov provides free services for unit test code coverage reporting and
> recent versions of the GitHub Action require a Codecov Token for reporting
> status. Apache Infra has assigned the {{CODECOV_TOKEN}} secret to the GitHub
> repository, so it can be used in GitHub workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13167) Replace Hamcrest Matchers with JUnit Matchers
[ https://issues.apache.org/jira/browse/NIFI-13167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13167: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace Hamcrest Matchers with JUnit Matchers > - > > Key: NIFI-13167 > URL: https://issues.apache.org/jira/browse/NIFI-13167 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Hamcrest 2.2 was released in 2019 and is the latest version available. A > small number of test classes use Hamcrest matchers instead of JUnit matchers > for assertions. The majority of these references do not provide any value > beyond what is available in JUnit 5. Although a small number of assert > methods can provide more useful failure messages, having a single library for > test assertions makes it easier to maintain tests across the repository. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13156) Replace use of com.fasterxml.jackson.core.JsonParser deprecated getCurrentName() with currentName() in JsonParser
[ https://issues.apache.org/jira/browse/NIFI-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13156: Fix Version/s: 1.27.0 > Replace use of com.fasterxml.jackson.core.JsonParser deprecated > getCurrentName() with currentName() in JsonParser > - > > Key: NIFI-13156 > URL: https://issues.apache.org/jira/browse/NIFI-13156 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M3, 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The getCurrentName() of com.fasterxml.jackson.core.JsonParser has been > deprecated and the suggested replacement is to use method currentName(). > This should be replaced in the following places > # > nifi-extension-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils/src/main/j > ava/org/apache/nifi/json/AbstractJsonRowRecordReader.java > # > nifi-extension-bundles/nifi-hubspot-bundle/nifi-hubspot-processors/src/main/java/org/apache/nifi/processors/hubspot/GetHubSpot.java > # > nifi-extension-bundles/nifi-salesforce-bundle/nifi-salesforce-processors/src/main/java/org/apac > he/nifi/processors/salesforce/QuerySalesforceObject.java > # > nifi-extension-bundles/nifi-shopify-bundle/nifi-shopify-processors/src/main/java/org/apache/nifi/processors/shopify/GetShopify.java > # > nifi-extension-bundles/nifi-zendesk-bundle/nifi-zendesk-processors/src/main/java/org/apache/nifi/processors/zendesk/GetZendesk.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13208) Increase member visibility in AbstractHadoopConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-13208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13208: Priority: Minor (was: Major) > Increase member visibility in AbstractHadoopConnectionPool > -- > > Key: NIFI-13208 > URL: https://issues.apache.org/jira/browse/NIFI-13208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Lehel Boér >Assignee: Lehel Boér >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > HADOOP_CONFIGURATION_RESOURCES access modifier should be changed to public in > order to used in any inherited class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13208) Increase member visibility in AbstractHadoopConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-13208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13208: Fix Version/s: 2.0.0-M3 1.27.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Increase member visibility in AbstractHadoopConnectionPool > -- > > Key: NIFI-13208 > URL: https://issues.apache.org/jira/browse/NIFI-13208 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Lehel Boér >Assignee: Lehel Boér >Priority: Minor > Fix For: 2.0.0-M3, 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > HADOOP_CONFIGURATION_RESOURCES access modifier should be changed to public in > order to used in any inherited class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13156) Replace use of com.fasterxml.jackson.core.JsonParser deprecated getCurrentName() with currentName() in JsonParser
[ https://issues.apache.org/jira/browse/NIFI-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-13156: Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Replace use of com.fasterxml.jackson.core.JsonParser deprecated > getCurrentName() with currentName() in JsonParser > - > > Key: NIFI-13156 > URL: https://issues.apache.org/jira/browse/NIFI-13156 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Daniel Stieglitz >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M3 > > Time Spent: 20m > Remaining Estimate: 0h > > The getCurrentName() of com.fasterxml.jackson.core.JsonParser has been > deprecated and the suggested replacement is to use method currentName(). > This should be replaced in the following places > # > nifi-extension-bundles/nifi-extension-utils/nifi-record-utils/nifi-json-record-utils/src/main/j > ava/org/apache/nifi/json/AbstractJsonRowRecordReader.java > # > nifi-extension-bundles/nifi-hubspot-bundle/nifi-hubspot-processors/src/main/java/org/apache/nifi/processors/hubspot/GetHubSpot.java > # > nifi-extension-bundles/nifi-salesforce-bundle/nifi-salesforce-processors/src/main/java/org/apac > he/nifi/processors/salesforce/QuerySalesforceObject.java > # > nifi-extension-bundles/nifi-shopify-bundle/nifi-shopify-processors/src/main/java/org/apache/nifi/processors/shopify/GetShopify.java > # > nifi-extension-bundles/nifi-zendesk-bundle/nifi-zendesk-processors/src/main/java/org/apache/nifi/processors/zendesk/GetZendesk.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13210) Add Codecov Token to GitHub Actions
David Handermann created NIFI-13210:
---
Summary: Add Codecov Token to GitHub Actions
Key: NIFI-13210
URL: https://issues.apache.org/jira/browse/NIFI-13210
Project: Apache NiFi
Issue Type: Improvement
Reporter: David Handermann
Assignee: David Handermann
Codecov provides free services for unit test code coverage reporting and recent
versions of the GitHub Action require a Codecov Token for reporting status.
Apache Infra has assigned the {{CODECOV_TOKEN}} secret to the GitHub
repository, so it can be used in GitHub workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13206:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13206:
Issue Type: Bug (was: Improvement)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
