sjyangkevin commented on PR #77138:
URL: https://github.com/apache/airflow/pull/77138#issuecomment-6950636381

   > Any reason why we want to do that?
   
   Hi @vincbeck , the main reason would be to invalidate outstanding tokens 
when a password is changed or reset. The fingerprint approach doesn’t require 
new DB entries/table and migration. I also tried to implement an approach that 
records a time per user, and checked against `iat`, but found that’s bit tricky 
to handle edge cases such as clock skew between API servers. After some 
exploration, I think the scope for this is only for FAB, because other auth 
managers handle this cycle outside of Airflow. Hope this answer the question 
and would appreciate any further feedback. Also, please feel free to correct me 
if you think something doesn’t seem to be right.


-- 
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]

Reply via email to