Couple of things to watch out for when applying CR’s to HCL Connections

I was updating a couple of Connections environments to CR4 and some of them are using SSO using OIDC and a custom database name for ICEC ( so not ESSAPPS)

After the install, the custom database name is overwritten, even with the correct database name in the response file, it seems to be hardcoded, second issue is that in an OIDC ( or SAML) environment you need to rename the filter in the oAuth trust association interceptor, but the CR installer creates a new one, so that one needs deleting after installing CR4