Hi Peter, 

Shib SPs couldn't interop with Satosa when it's acting as a SAML IDP?
Is there an issue about this anywhere with the details?

https://github.com/IdentityPython/SATOSA/issues/337

I believe it was this one. I spent some time talking with Ivan and Christos at a TechEx (or TNC?) about it several years ago. Honestly I don’t get how anyone could be using Satosa as an IdP, so perhaps I’m missing something vital. 

It’s possible it was fixed in https://github.com/IdentityPython/pysaml2/issues/738 - when I get some time I will test again with the latest version of Satosa.

Cheers,
Hannah

On 31 Jan 2023, at 10:59, Peter Schober <peter.schober@univie.ac.at> wrote:

* Hannah Short <hannah.short@cern.ch> [2023-01-31 08:55]:
I know the EOSC team were also enhancing Keycloak to support
federations properly.

"Were enhancing" as in "it's done and generally available"?
That would be good news, I suppose.

Do you have any examples of a public WAYF?

You mean other than https://seamlessaccess.org/ (which I already referenced)?

We were also planning to use Satosa as an outbound proxy to eduGAIN
for CERN users accessing eduGAIN SPs. When I tried this a few years
ago there were blocking issues with encryption to shibboleth SPs so
we had to roll back. I don’t know whether this is solved.

Shib SPs couldn't interop with Satosa when it's acting as a SAML IDP?
Is there an issue about this anywhere with the details?

-peter
_______________________________________________
satosa-users mailing list -- satosa-users@lists.sunet.se
To unsubscribe send an email to satosa-users-leave@lists.sunet.se