aminghadersohi opened a new pull request, #43786:
URL: https://github.com/apache/superset/pull/43786

   ### SUMMARY
   
   Skip session-invalidation enforcement for `/health`, `/healthcheck`, and 
`/ping` before resolving Flask-Login's `current_user` proxy. This keeps health 
probes independent of authentication, tenant context, and metadata-database 
access while retaining the existing fail-open behavior for all other requests.
   
   Adds regression coverage proving all three probe paths return before 
`current_user` can be resolved.
   
   Shortcut: https://app.shortcut.com/preset/story/119513
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   Not applicable (backend-only change).
   
   ### TESTING INSTRUCTIONS
   
   1. Run `pytest -q tests/unit_tests/security/test_session_invalidation.py`.
   2. Run `git add superset/security/session_invalidation.py 
tests/unit_tests/security/test_session_invalidation.py && pre-commit run`.
   3. Confirm `/health`, `/healthcheck`, and `/ping` remain available when 
authentication or tenant metadata resolution is unavailable.
   
   ### ADDITIONAL INFORMATION
   
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to