Hi there,
> Have you tried defining a IDPList array in your saml20-idp-remote.php file
> with the alternative entityIds for the IdP?
> It looks like it would work based on what the code is doing, but I don't
> see it as a documented feature.
>
> -Patrick
>
This does indeed work, and we have a couple of such setups. It is really
a workaround introduced by Jaime a couple of years back, because i
complained a lot over our most important use-case, where we employ
simplesamlphp basically as a proxy, being broken by a bit of tightening
up of the code.
I think, every release of simplesamlphp prior to 1.13 or so did in fact
not check, if the responder matched the target, and we had at that time
abused this neat little feature for years.
> On Monday, January 22, 2018 at 4:52:09 AM UTC-8, Francisco Almeida wrote:
>>
>> *I was asked to implement a USE CASE, where I should be able to accept a
>> SAML Response from a issuer that is different from the one I have sent the
>> request ("AuthnRequest").*
>>
>> After some DEBUG, I end up in this exception:
>> ----------------------------------------------
>>
>>>
>>> SimpleSAML_Error_Error: UNHANDLEDEXCEPTION
>>> Backtrace:
>>> 0 /var/simplesamlphp/www/module.php:180 (N/A)
>>> Caused by: SimpleSAML_Error_Exception: The issuer of the response does
>>> not match to the identity provider we sent the request to.
>>> Backtrace:
>>> 1 /var/simplesamlphp/modules/saml/www/sp/saml2-acs.php:97 (require)
>>> 0 /var/simplesamlphp/www/module.php:137 (N/A)
>>
>> ----------------------------------------------
>>
>> As far as I've gone this checks the SAML2 protocol message exchange.
>>
>> *My questions are: *
>> - Is this the USE CASE possible at all?
>> - If it is possible, how can I manage to configure this?
>> - If it is not possible, is this a protocol restriction? Where can i find
>> this Protocol Rule?
>>
>> Thanks for all the help in this issue.
>>
>> Thks,
>> Francisco
>>
Yours sincerely,
Bjorn