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
Describe the bug
1.- We receive a call on krakend
2.- There we validate the token comming from the UI
3.- We generate a client credentials token to call the backend
4.- Backend returns 301 with a url that works on the browser
5.- krakend returns 400 bad request with the below error:
InvalidAuthenticationInfo
Authentication information is not given in the correct format. Check the value of Authorization header.
RequestId:09ba3e43-f01e-0058-51b7-c1e59e000000
Time:2024-06-18T19:38:03.8875498Z
Expected behavior
I think krakend is trying to validate the token again after the redirect response but as we generated a different token to call backend now it has different information than the one validated, I would like to skip this second token validation for the redirect responses
Additional context
the error is not so clear I har to run everuthyng on my local host to be able to see what was happening
The text was updated successfully, but these errors were encountered:
martinsanchezpearltech
changed the title
Api gateways return 400 error related to authentication token
Api gateway return 400 error related to authentication token but the backend returned 301
Jun 18, 2024
martinsanchezpearltech
changed the title
Api gateway return 400 error related to authentication token but the backend returned 301
Api gateway returns 400 error related to authentication token but the backend returned 301
Jun 18, 2024
Environment info:
Describe the bug
1.- We receive a call on krakend
2.- There we validate the token comming from the UI
3.- We generate a client credentials token to call the backend
4.- Backend returns 301 with a url that works on the browser
5.- krakend returns 400 bad request with the below error:
InvalidAuthenticationInfo
Authentication information is not given in the correct format. Check the value of Authorization header.
RequestId:09ba3e43-f01e-0058-51b7-c1e59e000000
Time:2024-06-18T19:38:03.8875498Z
Your configuration file:
Commands used
How did you start the software?
Expected behavior
I think krakend is trying to validate the token again after the redirect response but as we generated a different token to call backend now it has different information than the one validated, I would like to skip this second token validation for the redirect responses
Logs
2024-06-18 13:37:59 2024/06/18 19:37:59 KRAKEND DEBUG: [CORS] 2024/06/18 19:37:59 Handler: Actual request
2024-06-18 13:37:59
2024-06-18 13:37:59 2024/06/18 19:37:59 KRAKEND DEBUG: [CORS] 2024/06/18 19:37:59 Actual response added headers: map[Access-Control-Allow-Credentials:[true] Access-Control-Allow-Origin:[*] Access-Control-Expose-Headers:[Content-Length, Content-Type] Vary:[Origin]]
2024-06-18 13:37:59
2024-06-18 13:38:04 [GIN] 2024/06/18 - 19:38:04 | 400 | 4.783303462s | 172.17.0.1 | GET "/my url"
Additional context
the error is not so clear I har to run everuthyng on my local host to be able to see what was happening
The text was updated successfully, but these errors were encountered: