https://bz.apache.org/bugzilla/show_bug.cgi?id=64537
--- Comment #4 from Cedric Roijakkers <[email protected]> --- I've given your patch a test, and indeed this seems to solve the issue. I've re-enabled the secret in our Tomcat application, and I can see the secret is now correctly being used in all different connection pools to the different Tomcat instances. The same configuration that was previously generating 403 errors is now working as expected. Would it be possible to backport this fix to the 2.4 branch for next release? For now, we'll just keep using this patch in our production environment. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
