SMAL

Did you consider to open a support case?

Install saml extension in your browser, and you will be able to compare both requests, in order to check where is the error.

Hi Seefan thank you for you responce I raise the support ticket

Hi david why i am not seen the Signature hashing Hashing Algorithm option in smal configuration is there any problem with configuration

Hi Stefan 
In SAML responses, the <NameID> element and the <Attribute> elements for emailaddress was different is this difference lead to 401 

I do not understand...... First of all, I would try to find where the error is located.. (using SAML Tools).

Hi David 

1. Idp1 SAML Response contains the following lines and it's working fine 

While IDP2 had it like this we geting 401 error in the interface 

2. Our generated Metadata file which we provided might have changed a little in terms of <md:RequestedAttribute> even if I guess that doesn’t matter, could that be a reason that it can’t authenticate?
   
   

The only differences between responses is only that line?

In our SAML responses, we've observed a difference between two identity providers (IdPs) in how the <NameID> and emailaddress attributes are handled:

• IdP1: The <NameID> and emailaddress are the same.
• IdP2: The <NameID> and emailaddress are different.

Against which attributes do you have mapped that values? Seems that the login is being made, but you don't have permissions in the platform

DO you see any error in logs?