-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INSPIRE Validator does not recognize ATOM certificate - Slovakia #1012
Comments
Dear @peterkysel27 , thank you for communicating the issue. Best regards, |
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, |
The staging version of the validator works well now. Thank you. |
Hello. Even the staging version is not working. Here is the error message: Thanks for your help. |
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, |
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... |
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, |
Thanks for the explanation. The staging version of the validator works well now with all our feeds. |
The fix for this issue is now available in the production instance. |
Hello,
we have the same problem as our colleagues from Spain here (#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:
And here is the error message:
error.txt
Thank you very much for your help.
Peter Kysel
The text was updated successfully, but these errors were encountered: