Upcoming change: API Gateway to access the Validator #769
Replies: 17 comments 1 reply
-
|
Dear INSPIRE validation community, To give the community the opportunity to test their own workflows against the new API Gateway while also ensuring business continuity, after the release the current endpoint of the Validator will remain available for a transition period of 3 weeks (i.e. until October 6, 2021). After this period, the INSPIRE Reference Validator will be only accessible through the public endpoint of the API Gateway. The API Gateway will impose a restriction on the rate and quota of the requests that any given user can send to the Validator. This limitations will be handled by the usage of API keys, which will be provided by the Validator team upon request from the organisations. The API key would need to be added as a header named The system is already available at https://y9tuozgmmc.execute-api.eu-west-1.amazonaws.com/validator/v2/ for anyone who wants to perform tests and adapt their applications to the upcoming test. Users and organisations interested in receiving an API key will need to contact the Validator team by sending an e-mail to
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @MarcoMinghini , thanks a lot for the information. Does the new API (v2021.3 - new UI) beside mentioned security improvements has some additional improvements/changes which affect clients (for example monitoring-bulk-validation-tool) which use API (v2021.1 - old UI)? For example:
|
Beta Was this translation helpful? Give feedback.
-
|
Dear all, The public access to the Validator will be dismissed in the next days, which means that, in order to access the Validator from outside the public UI, you will need an API key. If you do not yet have one, you need to contact the Validator team by sending an e-mail to
Finally, I would like to inform the users of API keys that, after receiving some requests and in order to allow for a better preparation of the upcoming INSPIRE Monitoring and Reporting, the limitations for the API key usage have been relaxed. API key users will receive an update via e-mail. |
Beta Was this translation helpful? Give feedback.
-
|
We have completed the migration to the API Gateway in the production instance. From now on, validations performed using the usual endpoint https://inspire.ec.europa.eu/validator/v2/ will get a 404 Not Found error. Once again, to use the Validator through the API (i.e. not from the UI) you will need to ask for an API key as described above. |
Beta Was this translation helpful? Give feedback.
-
|
As an addendum to this announcement, we recommend users to clear any cached files on their browser before using the validator (see #667 ), as the user interface now should point to a new endpoint for the API Gateway. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Is there any API service to retrieve the quotas available? |
Beta Was this translation helpful? Give feedback.
-
|
Dear @josegar74 , we're checking the API docs in case there is a public endpoint ot retrieve the quotas. Best |
Beta Was this translation helpful? Give feedback.
-
|
Dear @josegar74 , just an update. Best, |
Beta Was this translation helpful? Give feedback.
-
|
Hi there. I sent an email to get the Api-Key but received nothing ...what should I do? Thank you in advance |
Beta Was this translation helpful? Give feedback.
-
|
Dear @PaoloDiviacco, we are replying to your email. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much/Grazie mille
Paolo Diviacco
…______________________________________________________
Dott. Paolo Diviacco, PhD
Sezione di Geofisica
Istituto Nazionale di Oceanografia e di Geofisica Sperimentale - OGS
Borgo Grotta Gigante n. 42/c
34010 Sgonico (Trieste) - Italia
Tel. +39 040 2140380
www.inogs.it
On 13 Apr 2022, at 11:56, Fabio Vinci ***@***.***> wrote:
Dear @PaoloDiviacco <https://github.com/PaoloDiviacco>,
we are replying to your email.
—
Reply to this email directly, view it on GitHub <#594 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYWD6JN6U6OE3KAJS2Y7DRTVE2K6JANCNFSM5C3H3XZA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi there Thank you for sending the key...seemingly it works, but unfortunately after a couple of submissions it replies that we have exceeded the monthly quota ... Any suggestion? Thank you
|
Beta Was this translation helpful? Give feedback.
-
|
Dear @PaoloDiviacco, we checked the use of your API key and we detected that on April 13th you reached your weekly quota (200 requests). Could you try again? |
Beta Was this translation helpful? Give feedback.
-
|
Dear Fabio.
Thank you for your mail
This sounds very strange, we actually submitted only three records before being stopped.
Will check once more.
Anyway thank you for your reply.
Kind regards
Paolo
…______________________________________________________
Dott. Paolo Diviacco, PhD
Sezione di Geofisica
Istituto Nazionale di Oceanografia e di Geofisica Sperimentale - OGS
Borgo Grotta Gigante n. 42/c
34010 Sgonico (Trieste) - Italia
Tel. +39 040 2140380
www.inogs.it
On 28 Apr 2022, at 11:39, Fabio Vinci ***@***.***> wrote:
Dear @PaoloDiviacco <https://github.com/PaoloDiviacco>,
we checked the use of your API key and we detected that on April 13th you reached your weekly quota (200 requests).
This limit resets every Sunday at 00:00:00, so you should now be able to send new requests.
Could you try again?
—
Reply to this email directly, view it on GitHub <#594 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYWD6JLYRCMDI4QBZQEYNADVHJMGXANCNFSM5C3H3XZA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
Dear Fabio... strange behaviour continues. We sent only few records, seemingly there is a loop of validation attempts...maybe these increase the counter and then eventually we are cut off after the limit you mention...but the actual submissions are very few. What can we do? |
Beta Was this translation helpful? Give feedback.
-
|
Dear @PaoloDiviacco, indeed it's very strange, if there is a loop of validation attempts it could be a problem related to Geonetwork, have you tried to open an issue in the related repository? |
Beta Was this translation helpful? Give feedback.
-
|
An issue related to this error was opened in the GeoNetwork GitHub repository (geonetwork/core-geonetwork#6463). |
Beta Was this translation helpful? Give feedback.
-
|
I think Swagger docs https://inspire.ec.europa.eu/validator/swagger-ui.html (and probably other websites) are outdated because it doesn't explain details about how to get and use the new api key required. |
Beta Was this translation helpful? Give feedback.
-
Dear all,
this message is to inform you about a change we will introduce in the INSPIRE Reference Validator in the next release (v.2021.3) planned for mid-September (see the release plan).
Starting with this release, access to the Validator will be managed and controlled by an API Gateway. While this will have no impact on users using the Validator from the INSPIRE central User Interface, users using the Validator API from external clients will need a token to access the API.
More information on the access conditions as well as how organisations can request a token will follow here.
Beta Was this translation helpful? Give feedback.
All reactions