Closed lscorcia closed 11 months ago
I researched this and it is due to https://github.com/lscorcia/OpenAM-JEE-Agents/blob/9f49c1b9f367498bf93046902382ea0509f16eb6/jee-agents-distribution/jee-agents-distribution-tomcat-v6/src/main/assembly/config/configure.xml#L100-L104
According to the blame, this has been part of the logic since release 3.5 and it is tracked as OPENAM-2726: https://backstage.forgerock.com/docs/openam-jee-policy-agents/3.5/jee-release-notes/#key-fixes-3_5_0
Unfortunately I have no access to Jira and I cannot understand the reason behind this change. However, I'd say it's not really a problem, so I'll close the issue here with no changes.
Hi, when configuring a new agent on a Tomcat instance the installer modifies the
server.xml
and theweb.xml
files under webapps/, but does not add the filter to the globalweb.xml
config file. I think it used to do that automatically, but honestly have no idea when this behavior changed. I'll try to take a look at the code and see if there's anything obvious in there.