Hi Hans, good idea.
An example of a "standard" federation without issue
<federation id="..." name="saml20sp" protocolType="SAML20" spsPath="/isam/sps">
<partner name="SP ISAM DEV" protocolId="https://<myhost>/isam/sps/saml20sp/saml20" role="sp" self="true">
<endpoints>
<endpoint index="0" type="SAML2.SingleLogoutServiceInit" value="https://<myhost>/isam/sps/saml20sp/saml20/sloinitial"/>
And the Quickconnect federation with the issue :
<federation id="uuid247872c0-0173-1452-8107-a19c0939f9af" name="saml20idpqc" protocolType="SAML20" spsPath="/isam/sps">
<partner name="IBM Quick Connect" protocolId="https://<anotherhost>/isam/sps/saml20idpqc/saml20/sps/saml20idpqc/saml20" role="ip" self="true">
<endpoints>
<endpoint binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" index="0" type="SAML2.SingleSignOnService" value="https://<anotherhost>/isam/sps/saml20idpqc/saml20/sps/saml20idpqc/saml20/login"/>
The information is equivalent to the one I extracted vie the API.
------------------------------
Emmanuel Fauconnier
------------------------------
Original Message:
Sent: Mon July 20, 2020 05:24 AM
From: HANS VANDEWEGHE
Subject: Quick connect
Hi Emmanuel!
Would you be able to access the Fed runtime directly (might need to expose it to listen on an external IP, and use 'easuser' on the basic authentication prompt) to look at the /Info/InfoServiceXML endpoint?
This will give summary of the endpoints known by the AAC/Fed component.
This would be a good starting point, to see if the duplication already happens on the AAC/Fed component, or if somehow the Reverse Proxy introduces it.
Best regards,
Hans
------------------------------
HANS VANDEWEGHE
------------------------------