Update:
- 5:50PM Real-time monitoring of the infrastructure shows us that the latest difficulties are being resolved. Companies using SSO with ADFS and having encryption enabled should remove the old certificate and add the new one. More details have been added in the article about this specific configuration. Please feel free to open a support ticket through your Rainbow reseller if you are still experiencing problems.
- 4:00PM Some of you are reporting difficulties logging into SSO as a result of this certificate change. We are currently analyzing each situation in detail, but we strongly recommend that you re-download and re-apply the Rainbow metadata without further delay.
The SAML certificate provided in Rainbow metadata will expire July 19th, 2021. That's why, a new self signed certificate has been generated and has been added into Rainbow metadata the 09th of July. Companies using an OIDC-based SSO are not affected by this message.
Transition phase:
Since July 9th until July 15th (EMEA) and July 16th (NAR/CALA/CN/APAC), 2 certificates will be listed in Rainbow metadata.xml: the old one as principal certificate and the new one as alternate.
Final phase:
July 15th (EMEA) and July 16th (NAR/CALA/CN/APAC) the old certificate will be definitely removed from metadata.
We advise concerned company admins to download the new metadata.xml file from Rainbow Security SAML configuration menu and to upload it into their Identity Provider.
Warning: For companies having activated SAML signature in SAML advanced options, this step MUST be done before July 15th to avoid any SSO authentication failure.
More information about this procedure can be found here!
Commentaires
1 commentaire
Bonjour,
Deux certificats présentés pour la signature génèrent une erreur sur ADFS.
Un certificat auto signé n'est pas reconnu par les postes et n'est pas une bonne pratique.
Nous sommes en panne depuis hier matin et notre integrateur ne parvient pas à vous avoir...
Vous devez vous connecter pour laisser un commentaire.