CIE Backend

[peppelinux]

Starting from a SAML2 vanilla backend like the default one available in Satosa https://github.com/italia/Satosa-Saml2Spid/blob/master/example/plugins/backends/saml2_backend.yaml

i believe that it would be trivial to configure, without any code customization, a CIE backend and also have it in the TargetRouting map, here: https://github.com/italia/Satosa-Saml2Spid/blob/master/example/plugins/microservices/target_based_routing.yaml

@MdreW are you looking also for a CIE backend? That's a good issue for newcomers if you agree

[MdreW]

Hi @peppelinux, yes for me is CIE's time! I can try to write a CIE backend copying from your SPID backend, but I counting on your supervision :+1:

[peppelinux]

Don't do that, just Use a different configuration of the preexisting Saml2 backend, CIE should work as SAML2-core commands!

(hopefully)

Just put your note/questions about how to have a CIE compliant configuration, using the backend yaml file only, we'll see together if something won't fit

[peppelinux]

Here, for example, you can ave a tuple of three elements, with the last containing the preferred ACS index https://github.com/italia/Satosa-Saml2Spid/blob/2266149f71e33fac8f58c28fb6f8b6d9a234923b/example/plugins/backends/saml2_backend.yaml#L71

https://pysaml2.readthedocs.io/en/latest/howto/config.html?highlight=Tuple#endpoints

[peppelinux]

https://docs.italia.it/italia/cie/cie-manuale-tecnico-docs/it/master/federazione.html#federazione at [2.3.6. Esempio di metadata]

As we can see the metadata is a pure SAML2 compliances if it were not for the ContactPerson Extensions ... I'd like to have the metadata creation automatic, as have been done for SPID.

So, I made this commit to have an inheritable method for CIE, starting from Spid profile https://github.com/italia/Satosa-Saml2Spid/commit/fca9938419e2261d868d7eb9fbd83c4e24d9ed8f

[peppelinux]

Closed by https://github.com/italia/Satosa-Saml2Spid/releases/tag/v0.9.0