search

INSPIRE-MIF / helpdesk-validator

Community discussion forum for INSPIRE validation issues
41 stars 22 forks source link

INSPIRE Validator does not recognize ATOM certificate - Slovakia #1012

Closed peterkysel27 closed 4 months ago

peterkysel27 commented 7 months ago

Hello, we have the same problem as our colleagues from Spain here (https://github.com/INSPIRE-MIF/helpdesk-validator/issues/1008). When we try to validate an ATOM (no matter if I use production or staging validator), we get an error message.

Link to the ATOM: https://opendata.skgeodesy.sk/atom/INSPIRE_AU_dlsFeed.atom

If we tried the ATOM on another server (for example on https://ako.vugk.sk/atom/INSPIRE_AU_dlsFeed.atom), the validator works normally. So we think the problem could be with the certificate.

Here is our certificate: certificate

And here is the error message: error.txt

Thank you very much for your help. Peter Kysel

jenriquesoriano commented 6 months ago

Dear @peterkysel27 ,

thank you for communicating the issue. We will proceed to include the certificate in the Staging Instance and come back to you as soon as it is updated and ready to test.

Best regards,

DanielMartinPerezdeLeon commented 6 months ago

Dear @peterkysel27 ,

Thank you for bringing this issue to our attention.

We've successfully incorporated the certificate into our staging deployment, resolving the accessibility problem for the ATOM. You can verify it and use other urls on http://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/home/index.html.

Furthermore, rest assured that this certificate will be included in the upcoming official release of the VALIDATOR. Should you encounter any additional issues or have further feedback, please don't hesitate to reach out to us.

Regards,

peterkysel27 commented 6 months ago

The staging version of the validator works well now. Thank you.

peterkysel27 commented 4 months ago

Hello. Is this change already included in the production version of the validator? When I tried to validate our ATOM Feed today, I got the same error as before... image

Even the staging version is not working. Here is the error message: error2.txt Could it be the problem that there was a new certificate issued? (see the picture below) certificate2

Thanks for your help. Peter Kysel

DanielMartinPerezdeLeon commented 4 months ago

Dear @peterkysel27,

Thank you for notifying us about this problem. It seems the certificate for opendata.skgeodesy.sk expired just a few days after we released the next validator version. We have updated it in our staging environment, so you can keep testing in there.

Furthermore, rest assured that the certificate will be updated in the upcoming hot-fix of the VALIDATOR coming soon. Should you encounter any additional issues or have further feedback, please don't hesitate to reach out to us.

Regards,

peterkysel27 commented 4 months ago

Thank you, the staging version is working properly now. But what could be the reason that it is not working after the certificate is issued? When we tried to put the feeds to another server with another adress (ako.vugk.sk) for testing purposes, the validator was working properly without having to write to you to include the certificate in the validator...

DanielMartinPerezdeLeon commented 4 months ago

Dear @peterkysel27,

It looks like the certificate we used for opendata.skgeodesy.sk was valid only until february 20th. Consequently, any VALIDATOR instance utilized until that date should have been able to access the portal resources without issues.

We have updated the certificate in the staging environment, so any other instances should not be able to test opendata.skgeodesy.sk resources unless the certificate is updated in the .../res folder of the Dockerfile image ZIP archive (We will be uploading this change in a release soon, but if you need any help with this beforehand you can contact us).

Essentially, the issue seems to be a matter of timing. If you require further clarification or assistance with updating the certificate or any other aspect, please don't hesitate to reach out. We're here to help and any further questions or details about this topic is appreciated, so please feel free to reply with any other questions.

Regards,

peterkysel27 commented 4 months ago

Thanks for the explanation. The staging version of the validator works well now with all our feeds.

fabiovinci commented 4 months ago

The fix for this issue is now available in the production instance. For further details, please visit the v2024.0.1 release notes.