Hi I upgraded a DC Master and DC backup to 4.2-0 and then through to 4.2-1 (errata 85) tonight. I've encountered a few niggles that it seems some in the german forum might have already hit?
I think I've hit the issue noted in this bug: https://forge.univention.org/bugzilla/show_bug.cgi?id=42986
I can't login to the DC Backup web interface anymore. I just receive the "Could not fulfill the request. The SAML response contained a invalid signature: Failed to verify signature" error others seem to have had (reading via google translate). As far as I'm aware my CA/certs were not expired prior to the upgrade.
I think I'll hold off upgrading a 4.1 member server to 4.2 until I can determine it won't also have the SAML errors.
I've also got an issue in the DC Master where I can't seem to get updates via https. It seemed really similar to this other report in the german forum and his solution also helped me to get the packages over http instead to allow the upgrade from 4.2-0 to 4.2-1 to proceed.
Didn't have this issue on 4.1 and don't have this issue on the DC Backup (hence I think that can eliminate our network).