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
This is a high-level issue to address the following concern:
How do we verify that a write-request (HTTP POST) originates from a real deis cluster?
We don't want to overly complicate things and, say, store user credentials. But we would like, longer term, to disallow random folks from reverse engineering our elegantly designed API and sending us bogus data.
The text was updated successfully, but these errors were encountered:
We're currently considering rate limiting as a stratagem to address this. We're no longer seriously considering actually identifying cluster requests as coming from "real" clusters.
This is a high-level issue to address the following concern:
We don't want to overly complicate things and, say, store user credentials. But we would like, longer term, to disallow random folks from reverse engineering our elegantly designed API and sending us bogus data.
The text was updated successfully, but these errors were encountered: