I'm not concerned about the Log4J in 6.3.7.2, a gradlew clean build
fixed that up...but curious about any big mismatches with
mfa-gauth/mongo that could be causing the exception stack below.
Specifically "java.lang.IllegalArgumentException: Collation not
supported by wire version: 4"
C
On
Baba,
You want 6.3.7.3.
Make sure you clean before you build.
./gradlew clean build
Ray
On Wed, 2021-12-15 at 21:51 +, Baba Ndiaye wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
Eventually
Eventually i'm using JSON for service registry but i have this
unzip -l /var/lib/tomcat9/webapps/cas.war
s.war | grep log4j
35359 2021-12-15 21:05 WEB-INF/lib/log4j-web-2.16.0.jar
21248 2021-12-15 21:05 WEB-INF/lib/log4j-slf4j18-impl-2.16.0.jar
1789565
As a longer view on Log4J mitigation we are doing test upgrades from
6.2.x to 6.3...
We are using Mongo for service registry, ticketregistry and GAuth registry.
When testing the GAuth functions we are getting an exception from the
following mongo related error.
2021-12-15 21:15:06,696
