+1 It was explained to me that what I had brought up earlier is normal behavior.
Thanks for RM'ing David! On Wed, Dec 17, 2025 at 2:14 PM Dan S <[email protected]> wrote: > I am not sure whether I am seeing expected behavior or not for controller > services which in 2.7.0 were only invalid in my NIFI instance since they > had bogus values for properties but now in 2.7.2 these same controller > services in addition to being invalid state have log error messages > indicating failure to invoke @OnEnabled method. I have posted the screen > shots on the dev channel in Slack to show the difference between 2.7.0 and > 2.7.2. > > On Wed, Dec 17, 2025 at 10:42 AM Kevin Doran <[email protected]> wrote: > >> +1 binding >> >> On Wed, Dec 17, 2025 at 7:47 AM Joe Witt <[email protected]> wrote: >> > >> > +1 binding >> > >> > usual checks >> > >> > On Wed, Dec 17, 2025 at 2:42 AM Pierre Villard < >> [email protected]> >> > wrote: >> > >> > > +1, binding >> > > >> > > Thanks David! >> > > >> > > Le mar. 16 déc. 2025 à 22:08, David Handermann >> > > <[email protected]> a écrit : >> > > > >> > > > Kay-Uwe, >> > > > >> > > > Thanks for double-checking and following up, testing the release >> > > > candidate is very much appreciated! >> > > > >> > > > Regards, >> > > > David Handermann >> > > > >> > > > On Tue, Dec 16, 2025 at 2:58 PM [email protected] < >> [email protected]> >> > > wrote: >> > > > > >> > > > > David, >> > > > > >> > > > > You're right. I don't know why it didn't work. >> > > > > I reinstalled NiFi 2.7.2 and now it works (and, most importantly, >> with >> > > > > the previous login-identity-providers.xml). >> > > > > >> > > > > Everything is working as expected. >> > > > > I take it all back and say: >> > > > > >> > > > > +1 (non-binding) >> > > > > >> > > > > Regards, >> > > > > Kay-Uwe Moosheimer >> > > > > >> > > > > Am 16.12.25 um 21:28 schrieb David Handermann: >> > > > > > Kay-Uwe, >> > > > > > >> > > > > > Thanks for confirming that the Reporting Task is working as >> expected. >> > > > > > >> > > > > > On a new installation, a new random username and password would >> be >> > > generated. >> > > > > > >> > > > > > It sounds like something else changed in your local >> configuration. If >> > > > > > you are able to copy the previous login-identity-providers.xml, >> the >> > > > > > same password should work as expected. >> > > > > > >> > > > > > Regards, >> > > > > > David Handermann >> > > > > > >> > > > > > On Tue, Dec 16, 2025 at 2:12 PM [email protected] < >> > > [email protected]> wrote: >> > > > > >> -1 (non-binding) >> > > > > >> >> > > > > >> The reporting tasks now appear to be set correctly. NiFi >> starts and >> > > the >> > > > > >> UI is accessible. >> > > > > >> However, in the standalone version, the previously set >> password is >> > > no >> > > > > >> longer correct: >> > > > > >> >> > > > > >> 2025-12-16 20:51:38,787 INFO [NiFi Web Server-72] >> > > > > >> o.a.n.w.a.c.IllegalArgumentExceptionMapper >> > > > > >> java.lang.IllegalArgumentException: The supplied username and >> > > password >> > > > > >> are not valid.}. Returning Bad Request} response. >> > > > > >> java.lang.IllegalArgumentException: The supplied username and >> > > password >> > > > > >> are not valid. >> > > > > >> at >> > > > > >> >> > > >> org.apache.nifi.web.api.AccessResource.createAccessToken(AccessResource.java:143) >> > > > > >> at >> > > > > >> >> > > >> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) >> > > > > >> at >> > > java.base/java.lang.reflect.Method.invoke(Method.java:580) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:146) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:189) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:176) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:93) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:470) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:394) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:80) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:274) >> > > > > >> 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:253) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:422) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:374) >> > > > > >> at >> > > > > >> >> > > >> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:355) >> > > > > >> ... >> > > > > >> Caused by: >> > > > > >> >> > > >> org.apache.nifi.authentication.exception.InvalidLoginCredentialsException: >> > > > > >> Password verification failed >> > > > > >> at >> > > > > >> >> > > >> org.apache.nifi.authentication.single.user.SingleUserLoginIdentityProvider.authenticate(SingleUserLoginIdentityProvider.java:92) >> > > > > >> at >> > > > > >> >> > > >> org.apache.nifi.web.security.spring.LoginIdentityProviderFactoryBean$1.authenticate(LoginIdentityProviderFactoryBean.java:284) >> > > > > >> at >> > > > > >> >> > > >> org.apache.nifi.web.api.AccessResource.createAccessToken(AccessResource.java:134) >> > > > > >> ... 95 common frames omitted >> > > > > >> >> > > > > >> >> > > > > >> No problem, quickly create a new one with: >> > > > > >> bin/nifi.sh set-single-user-credentials USERNAME PASSWORD >> > > > > >> >> > > > > >> login-identity-providers.xml is adjusted/rewritten. >> > > > > >> >> > > > > >> But once again, it is not possible to log in. The same error >> message >> > > > > >> appears. >> > > > > >> >> > > > > >> It looks as if it is not possible to log in to the standalone >> > > version?! >> > > > > >> Can that be true? >> > > > > >> Or is there a new procedure? >> > > > > >> >> > > > > >> -Kay-Uwe >> > > > > >> >> > > > > >> >> > > > > >> Am 16.12.25 um 20:01 schrieb David Handermann: >> > > > > >>> Team, >> > > > > >>> >> > > > > >>> I am pleased to be calling this vote for the source release of >> > > Apache >> > > > > >>> NiFi 2.7.2. >> > > > > >>> >> > > > > >>> Please review the following guide for how to verify a release >> > > candidate build: >> > > > > >>> >> > > > > >>> >> > > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification >> > > > > >>> >> > > > > >>> The source being voted on the and the convenience binaries are >> > > > > >>> available on the Apache Distribution Repository: >> > > > > >>> >> > > > > >>> https://dist.apache.org/repos/dist/dev/nifi/nifi-2.7.2 >> > > > > >>> >> > > > > >>> The build artifacts are available on the Apache Nexus >> Repository: >> > > > > >>> >> > > > > >>> >> > > >> https://repository.apache.org/content/repositories/orgapachenifi-1328/ >> > > > > >>> >> > > > > >>> Git Tag: nifi-2.7.2-RC2 >> > > > > >>> Git Commit ID: 098c97460988449ef4fba5508a83b20cc65ce9ab >> > > > > >>> GitHub Commit Link: >> > > > > >>> >> > > >> https://github.com/apache/nifi/commit/098c97460988449ef4fba5508a83b20cc65ce9ab >> > > > > >>> >> > > > > >>> Checksums of nifi-2.7.2-source-release.zip >> > > > > >>> >> > > > > >>> SHA512: >> > > >> 77df329f183fbbe51764abbe004f70e07d97ccb64f1ab0c04d20a471b4a613a5ac5eadb3555a098ce0c77722c67983a4724ba3dbc4c7f0ebcbfa6ac6fc049ba5 >> > > > > >>> >> > > > > >>> Release artifacts are signed with the following key: >> > > > > >>> >> > > > > >>> https://people.apache.org/keys/committer/exceptionfactory.asc >> > > > > >>> >> > > > > >>> KEYS file is available on the Apache Distribution Repository: >> > > > > >>> >> > > > > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS >> > > > > >>> >> > > > > >>> Issues resolved for this version: 11 >> > > > > >>> >> > > > > >>> >> > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12356562 >> > > > > >>> >> > > > > >>> Release note highlights can be found on the project wiki: >> > > > > >>> >> > > > > >>> >> > > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.7.2 >> > > > > >>> >> > > > > >>> In light of the limited nature of this release candidate, the >> vote >> > > > > >>> will be open for 24 hours. >> > > > > >>> >> > > > > >>> Please download the release candidate and evaluate the >> necessary >> > > items >> > > > > >>> including checking hashes, signatures, build from source, and >> test. >> > > > > >>> Then please vote: >> > > > > >>> >> > > > > >>> [] +1 Release this package as nifi-2.7.2 >> > > > > >>> [] +0 no opinion >> > > > > >>> [] -1 Do not release this package because... >> > > >> >
