bmanan7 opened a new issue, #60402:
URL: https://github.com/apache/airflow/issues/60402

   ### Apache Airflow Provider(s)
   
   fab
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-fab==1.5.3
   
   ### Apache Airflow version
   
   2.11.0
   
   ### Operating System
   
   Debian GNU/Linux
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   Astronomer Software 0.34.1, Astro Runtime 2.11.0+astro.3, FAB auth manager 
(/auth/fab/v1/).
   
   ### What happened
   
   Editing a user's email or username from the Airflow UI succeeds, but the 
ab_user.changed_on column in the metadata DB does not change. Only 
`created_on/last_login` change; changed_on stays at the original timestamp.
   
   Verified via SQL: SELECT id, username, email, created_on, changed_on, 
last_login FROM ab_user ORDER BY changed_on DESC LIMIT 50;
   
   ### What you think should happen instead
   
   When a user's fields (email/username) are modified in the UI, 
ab_user.changed_on should reflect the modification time (update timestamp).
   
   ### How to reproduce
   
   1. Log in to Airflow as an admin user.
   2. Go to Security -> List Users.
   3. Edit an existing user (change email or username or roles) and save.
   4. Query the metadata DB before and after the edit:
   ```
   SELECT id, username, email, created_on, changed_on, last_login
   FROM ab_user
   WHERE username = '<target_username>';
    ```
   5. Observe that changed_on does not change after the update.
   
   
   ### Anything else
   
   This problem occurs every time. Role assignments also mutate user state. 
Even when only roles are changed (no profile fields), we would expect 
ab_user.changed_on to update to reflect the latest user modification.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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