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

   ### Apache Airflow version
   
   2.5.1
   
   ### What happened
   
   We're using an Azure OAUTH based login in our Airflow implementation, and 
everything works great. This is more of a visual problem than an actual bug.
   
   In the Audit logs, the `owner` key is mapped to the username, which in most 
cases is airflow. But, in situations where we manually pause a DAG or enable 
it, it is mapped to our generated username, which doesn't really tell one who 
it is unless they were to look up that string in the users list. Example:
   
   
![image](https://user-images.githubusercontent.com/102953522/220382349-102f897b-52c4-4a92-a3e1-5b8a1b1082ff.png)
   
   It would be nice if it were possible to include the user's first and last 
name alongside the username. I could probably give this one a go myself, if I 
could get a hint on where to look.
   
   I've found the dag_audit_log.html template, but not sure where to change 
log.owner. 
   
   ### What you think should happen instead
   
   It would be good to get a representation such as username (FirstName 
LastName).
   
   ### How to reproduce
   
   N/A
   
   ### Operating System
   
   Debian GNU/Linux 11
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Deployed with Helm chart v1.7.0, and Azure OAUTH for login.
   
   ### Anything else
   
   _No response_
   
   ### 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