Connexion SSO AzureAD Fail [FR][EN]

Answered

January 22, 2021 07:17

Bonjour,

J'ai suvi la procedure pour activer le SSO via Azure AD et rien n'y fait, j'ai bien dans les log d'Azure des success comme quoi, la connexion marche mais sur Rainbow, je me retrouve avec ces messages. Soit l'un soit l'autre en fonction de si je passe par Rainbow (erreur 1) ou le test de connexion azure (erreur 2)

"SAML Assertion signature check failed! (checked 1 certificate(s))" (error code: 500000)

"Assertion can't be decrypted: cookie 'SamlRequestId' is missing" (error code: 400000)

Merci d'avance pour votre aide.

Hi,

I make and remake all the procedure https://support.openrainbow.com/hc/fr/articles/360008866099-How-to-Activate-the-Single-Sign-On-between-Azure-Active-Directory-and-my-Company-using-SAML-EN-

When i check Azure AD log, i see it's granted, but when i test, I have 2 errors:

"SAML Assertion signature check failed! (checked 1 certificate(s))" (error code: 500000)

"Assertion can't be decrypted: cookie 'SamlRequestId' is missing" (error code: 400000)

Have you an idea?

Thanks

Comments

11 comments

Claire DECHRISTE

January 22, 2021 08:51
Hello,

Please send me an IM through Rainbow, I will try to help you on this.

Regards,

Claire Dechristé
0

Comment actions Permalink
Jordan LECANU

January 22, 2021 10:11
Hello,

Thanks for your help, how can i send you a IM?
0

Comment actions Permalink
Claire DECHRISTE

January 22, 2021 18:31
Hello,

My Rainbow user (claire.dechriste@al-enterprise.com) is public, you can invite me to join your network in Rainbow.
0

Comment actions Permalink
Bernhard NOWAK

January 25, 2021 14:41
Hi!

We get the same error. Is this a known issue?

Regards,

Bernhard
0

Comment actions Permalink
Claire DECHRISTE

January 25, 2021 16:46
Hello,

An issue might happen in some cases on new SAML configurations since the introduction of Advanced parameters.

It will be fixed in next version 83.

But meanwhile here is a workaround:

Select SAML "Advanced options", first uncheck, then check again the box "allow unencrypted assertion", then save the configuration.

If this does not work, please open a case on Rainbow support side.

Regards,

Claire Dechristé
0

Comment actions Permalink
Jordan LECANU

February 02, 2021 09:34

Edited
Hello,

the version 83 is avaliable and i have again the same error 500000

I don't find how to open a case.

When i go in a user profile in security, i choose connection method SSO, a new field appear "id authentification", what's information is needed?

Thanks
0

Comment actions Permalink
Antonio SPIRANDELLI

February 04, 2021 21:26
Hi, i'am facing same issue. Versione 83 is out.

How can we solve?
0

Comment actions Permalink
Claire DECHRISTE

February 05, 2021 07:53
Hi,

The root cause might be the issue stated previously if SSO configuration was initiated between v82 and 83.

Or it might be a wrong certificate or something else...

Please contact your ALE partner to open ticket on ALE support.

Regards.

Claire
0

Comment actions Permalink
Jordan LECANU

February 08, 2021 10:31
Hello,

I have a answer to my partner, between 82 and 83 version, the certificate is renewed, i change it in Rainbow settings and it's OK for us
0

Comment actions Permalink
Norbert LAJOIE

February 17, 2021 18:59
Hello,

I still have today the same issue :

I tried different solution but ... nothing works ...

How can I open a ticket on ALE support please ?

Best regards,
0

Comment actions Permalink
Claire DECHRISTE

February 18, 2021 09:05
Hello,

- If you are an ALE Business Partner, you can, as with other ALE products, open a ticket on the business portal (https://businessportal.al-enterprise.com/).
- If you are an end customer managed by an ALE Business Partner, please contact them.
- If you are an end user not yet managed by an ALE Business Partner, you can send your question to Emily directly from Rainbow by adding #support to your message or to post your question in the Help, Assistance & Support community (https://support.openrainbow.com/hc/en-us/community/topics/115000066190-Help-Assistance-Support).

Thanks.
0

Comment actions Permalink