Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.7k
Add support for error headers in auth callout handlers#7500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
Signed-off-by: Andrási István <isiandrasi@gmail.com>
neilalexander left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM principally but would like@aricart to take a look too.
Also wondering if we should update theAuth Callouts ADR.
ripienaar commentedNov 5, 2025
All significant content the server react on from the auth callout service must be signed and verifiable imo. If your service can't sign then thats something to log in the service logs. Conceptually I am not sure we can just start acting on unsigned/unverifiable information here |
istvan-andrasi commentedNov 5, 2025
Since it's just a small QoL improvement for the callout service developer, if it raises concerns on the server side, it's probably not worth it. |
ripienaar commentedNov 5, 2025
For background when we added the error feedback in the JWT my actual feature request was to have a header the server would just log - essentially exactly this. But at the time we got the current behaviour instead for the reasons I mentioned :) |
Uh oh!
There was an error while loading.Please reload this page.
Signed-off-by: Andrási Istvánisiandrasi@gmail.com
Resolves#7501