Has anyone run into anything unexpected after installing 2021 U7 or 2018 U17? We haven't so far.

Nor have we. All of our 2018 and 2021 servers have been updated (including production) as of mid-afternoon yesterday.

I had a Windows CF2018 system freeze and I had to force a reboot at the Hosting level after update. My LINUX CF2021 updates were a breeze.

This is good to hear.

so far so good. we did have some security scanners freak out about some log4j stuff in the backup folder where it stashes things that have been updated, but we expect that deleting those class files will solve it.

@SteveJ glad to hear we’re not the only ones still dealing with that. we’ve taken to moving those backup folders to long-term off-line storage shortly after applying the updates so we still have them if needed but to keep the scanner team’s knickers less twisty. we’re still fending them off repeatedly on the

cf-logging.jar

files’s Log4j classes, though, as whatever mechanism they use for this type of proctology isn’t happy with what it finds in there.

@rstewart - that's the problem with these automated scanners - they're not smart enough to know what code is being run and what is just sitting in an archive. it has even complained about log4j files sitting in someone's trash!

@SteveJ Yup, same same. Our scanner teams must be using similar tools/approaches/brain cells. :)

Only issue we ran into with CF2021 after applying update 7 was needing to uninstall and reinstall the saml2 package. Did that through CF admin without a reboot or restarting the service and were good to go.