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
We deploy the Onyx service in kubernetes and have the application behind a custom ingress that validates authentication with a JWT in the Authorization Bearer header.
It appears a change in PR #3423 began raising a ValueError when a Bearer token in the authorization HTTP header is unfamiliar. This is causing 4XX errors throughout the application in our deployment now. This worked fine on v0.15.0. and presented after upgrading to the new Onyx-named app on v0.19.0.
If we move this app behind an kubernetes ingress without this header and enable basic-auth, the app begins working correctly. The error seen prints the first three characters of a JWT (eyJ) so our issue indeed seems to be caused by this recent change.
The text was updated successfully, but these errors were encountered:
We deploy the Onyx service in kubernetes and have the application behind a custom ingress that validates authentication with a JWT in the Authorization
Bearer
header.It appears a change in PR #3423 began raising a ValueError when a
Bearer
token in the authorization HTTP header is unfamiliar. This is causing 4XX errors throughout the application in our deployment now. This worked fine on v0.15.0. and presented after upgrading to the new Onyx-named app on v0.19.0.If we move this app behind an kubernetes ingress without this header and enable basic-auth, the app begins working correctly. The error seen prints the first three characters of a JWT (
eyJ
) so our issue indeed seems to be caused by this recent change.The text was updated successfully, but these errors were encountered: