shibboleth Idp attributes with vendor SP using Samly
peter.schober at univie.ac.at
Thu Jul 16 10:26:50 UTC 2020
* Jehan PROCACCIA <jehan.procaccia at tem-tsp.eu> [2020-07-15 20:42]:
> I did not update idp v3 to v4
> I created a completly new VM aside the v3
> that new VM is centos 8 , java 11, tomcat 9 , it has it's own new EntityID and hence new cert and new metadata.
So is this all just a toy/test/demo environment?
Why else would you ever change your entityID -- as part of a software
upgrade or otherwise?
So if this is a completely different IDP (new entityID, new endpoints,
new keys) everything you said about IDPv3 working with this SP is
pretty much irrelevant, I guess.
IMO this thread simply comes down to using a fresh IDPv4 instance with
that specific SP implementation. Since we already identified the
likely source of the error (see my previous post) the only thing left
to do here is picking the right certificate to manually configure into
the SP, with no changes to the IDP's default configuration /at all/.
More information about the users