🛡️ Sentinel: Prevent sensitive error detail leakage in auth decorator - #29
Conversation
Remove raw exception strings ('details': str(e)) from the 401 Unauthorized
response payload in login_required decorator to prevent exposing internal
backend error details to unauthenticated clients. Standardize on server-side
logging for authentication failures.
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
🛡️ Sentinel Security Fix
@login_requireddecoratordetails: str(e)from the 401 JSON response inauth/utils.pyand added server-side logging (logger.warning).tests/test_auth.pyand ranPYTHONPATH=src:. pytestto verify error payloads do not leak internal exception details.PR created automatically by Jules for task 11436214463133502657 started by @Pmaster-dev