Issues after upgrading SAML-module

0
Hi all, After I upgraded the SAML-module from v1.3 (Mx 5.21.1) to v1.8.4 (Mx 6.10.10) I encounter some issues on runtime. 1. 'The following certificate is being used twice' Dec 19 14:37:26.270 - INFO - SAML_SSO: Loading urn:oasis:names:tc:SAML:2.0:protocol metadata from /srv/cloud/slots/tr10000/deploy/data/tmp/saml_IdPFile1513690646269.xml Dec 19 14:37:26.493 - WARNING - SAML_SSO: The following certificate is being used twice: CN=KlantTest::CN=Root Agency Dec 19 14:37:26.546 - INFO - SAML_SSO: Loading urn:oasis:names:tc:SAML:2.0:protocol metadata from /srv/cloud/slots/tr10000/deploy/data/tmp/saml_IdPFile1513690646545.xml (I changed the real Client name in 'Klant')   2. saml/assertion Dec 20 10:19:51.812 - ERROR - Connector: 404 - file not found for file: saml/assertion I didn't change the configuration (should I?), the SSO en SAML RequestHandlers are still in place also. The CustomUserProvisioning-microflow contains some client specific actions with some extra logmessages, but it seems that this microflow is not even activated (no logmessages found), probably because of the issues I described.  I really appreciate any help you can provide
asked
1 answers
0

You might want to try to do a clean setup. Just create another idP configuration and do all the steps again. And for you the second point check you Network settings. You should have these settings below

Unless you changed your top level setting.

Regards,

Ronald

answered