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,
we are currently in pre-decision process and we might use the OpenGDPR specification.
I got one question: Are there reasons for not providing an GET endpoint on /opengdpr_requests/?
Besides the authentication issue. You somehow need to make sure that the request has the right to see the response.
If there no reasons against it, I would add it to the specification and create a PR for it.
The text was updated successfully, but these errors were encountered:
I am not particularly opposed, but it would have to be optional. We know of implementations that are using nosql backing stores where scans are either quite slow or not supported.
Nonetheless, even if supported, I would expect it to support paging with cursors and filtering by status. There can be many thousands to even millions of requests for large companies.
Hi,
we are currently in pre-decision process and we might use the OpenGDPR specification.
I got one question: Are there reasons for not providing an GET endpoint on /opengdpr_requests/?
Besides the authentication issue. You somehow need to make sure that the request has the right to see the response.
If there no reasons against it, I would add it to the specification and create a PR for it.
The text was updated successfully, but these errors were encountered: