When the mutator `hydrator` returns a 401, oathkee...
# talk-oathkeeper
h
When the mutator
hydrator
returns a 401, oathkeeper is propagating this error as
500 internal server error
, is this really the expected behavior?
s
should be
Bad gateway
probably 🤔
h
Feels like this should be configurable. Im working with a scenario where we put mappings in this hydrator, and if the mapping is missing, we want to return a 401 since the mapping is missing rather than a 5xx code that implies something else
s
hm I see
I suggest opening an issue and discussing it there
h
Alright, thanks for the quick answer 👍