-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Bug
Current behavior / bug description
If filter-proxy is unable to verify the authorization for a certain route, it gives "unauthorized request" as an error message.
Expected behavior
A message like "unable to verify authorization". The current behaviour may be confusing during debugging.
Steps to reproduce the behavior
- Make Atlas backend fail during authorization (in my case, it was failing because of Docker Compose setup on my system)
- Let Atlas make a request through filter-proxy and look at the filter-proxy log
Context
Possible solution
filter-proxy should check if Atlas indeed thinks the request is unauthorized (error code 401 or 403), around line 137 of main.go.
Environment
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels