You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I'm opening an issue to share my experience with spid-sp-test in order to improve this already awesome tool, as agreed with @peppelinux.
I'm following the procedure to become a CIE private SP and yesterday, when uploading my metadata to https://federazione.servizicie.interno.gov.it, I got the following error:
[/EntityDescriptor/Signature/KeyInfo/X509Data/X509Certificate] Certificato non valido.
It came out that there were no errors concerning the certificate, just a "Missing ContactPerson/Extensions/Private, this element MUST be present" (I had previously seen an issue on this repo dealing with that, so I knew it was not a problem in my case).
Hi there,
I'm opening an issue to share my experience with spid-sp-test in order to improve this already awesome tool, as agreed with @peppelinux.
I'm following the procedure to become a CIE private SP and yesterday, when uploading my metadata to https://federazione.servizicie.interno.gov.it, I got the following error:
[/EntityDescriptor/Signature/KeyInfo/X509Data/X509Certificate] Certificato non valido.
Therefore I analized the metadata with spid-sp-test, using the docker image http://ghcr.io/italia/spid-sp-test:latest.
It came out that there were no errors concerning the certificate, just a "Missing ContactPerson/Extensions/Private, this element MUST be present" (I had previously seen an issue on this repo dealing with that, so I knew it was not a problem in my case).
After that I updated the acs and logout endpoints' locations (I am using the CIE ID provider for keycloak https://github.com/lscorcia/keycloak-cieid-provider, so maybe my updates also affected something I might not be aware of 😃) and the next validation through https://federazione.servizicie.interno.gov.it passed as a charm.
Hope this can help 😄
The text was updated successfully, but these errors were encountered: