Primary and Replica on 5.2, Managed Node on 5.0

UCS - Univention Corporate Server
, ,
1

Hi@all,

I have updated my Primary Directory Node and the Replica to 5.2. However, I still have two Managed Nodes running apps that have not yet been migrated to 5.2 (e.g., NextCloud). On these two systems, I get the following in the system diagnostics:

Critical: SAML certificate check failed

Certificate https://ucs-sso.lan.meinedomain.de/simplesamlphp/saml2/idp/certificate could not be loaded: Unable to load certificate. See Frequently asked questions — Cryptography 46.0.0.dev1 documentation for more details.
Certificate https://192.168.83.5/simplesamlphp/saml2/idp/certificate could not be loaded: Unable to load certificate. See Frequently asked questions — Cryptography 46.0.0.dev1 documentation for more details.

Run the join script 92univention-management-console-web-server via the “Domain Join” module or with the command univention-run-join-scripts --force --run-scripts 92univention-management-console-web-server as root.

I have already forced all join scripts to run and restarted the systems, but this message is not resolved. The Primary no longer runs SimpleSAMLphp. What do I need to do on the Managed Nodes (5.0.x) to make this message disappear?

with best
sven

2

I had the same issue. And I wish I could remember how I got rid of it… probably by eliminating the last bit of single-sign-on I could hunt down, possibly going into the registry or, God forbid, even into the file system…

I managed to get rid of it, not that it ever did any harm–except to my nerves, but hopefully with NextCloud finally ready for 5.2, your holdups with regards to 5.2 are gone alltogether.