Implement a mechanism to allow unauthenticated requests for specific endpoints #258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a mechanism to allow unauthenticated requests for specific endpoints, and allows unauthenticated requests for
apply_constraintsandestimate_costendpoints.Details
Endpoints with forbidden unauthenticated requests requires an authentication header to be sent, otherwise return a
PermissionDeniederror.Endpoints with allowed unauthenticated requests doesn't require an authentication header to be sent, and in this case set the internal
user_uidvariable tounauthenticated.Also, the
Refererendpoint is now used to help determine the request origin in case the request is not authenticated: if it is present, the request origin is set toui, otherwise it is set toapi.Why it's useful
Before,
apply_constraintsandestimate_costdidn't required authentication, so they already allowed unauthenticated requests. For https://jira.ecmwf.int/secure/RapidBoard.jspa?rapidView=401&view=detail&selectedIssue=COPDS-2811&quickFilter=1278# and #257, though, we need a mechanism for: