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 should return forbidden only when the query can't find the tenant or the authentication is wrong. Otherwise, the error message should be different and an internal or unavailable error should be returned. This can happen when the database query returns an error (e.g. due to it being unavailable).
as this needs to be checked for a NotFound error, and then it should return a forbidden error if something is off with the jwt, and in all other cases a generic error with a 500 status code
The text was updated successfully, but these errors were encountered:
steebchen
changed the title
Improve error handling in event push
Improve error message in event push
Feb 6, 2024
This should return forbidden only when the query can't find the tenant or the authentication is wrong. Otherwise, the error message should be different and an internal or unavailable error should be returned. This can happen when the database query returns an error (e.g. due to it being unavailable).
hatchet/internal/services/grpc/middleware/auth.go
Lines 37 to 51 in 78685d0
An important part is this line
hatchet/internal/auth/token/token.go
Line 145 in 73adb77
as this needs to be checked for a NotFound error, and then it should return a forbidden error if something is off with the jwt, and in all other cases a generic error with a 500 status code
The text was updated successfully, but these errors were encountered: