[ 
https://issues.apache.org/jira/browse/AIRFLOW-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Lukyanchikov updated AIRFLOW-3442:
-----------------------------------------
    Description: 
When i start to use new RBAC feature with google oauth i notice that owner in 
audit logs shows as google_[some number]. Its pretty hard to understand how is 
actually make some changes or run dag. But if there will be first name second 
name or at least email it will be pretty easy without checking who is using 
this google_ username. Maybe it can be configured somehow, please advise

!Screen Shot 2018-12-04 at 12.41.50 PM.png!

  was:
When i start to use new RBAC feature with google oauth i notice that owner in 
audit logs shows as google_[some number]. Its pretty hard to understand how is 
actually make some changes or run dag. But if there will be first name second 
name or at least email it will be pretty easy without checking who is using 
this google_ username. Maybe it can be configured somehow, please advise

!Screen Shot 2018-12-04 at 12.41.50 PM.png|thumbnail!


> Show first and second name of user in audit logs
> ------------------------------------------------
>
>                 Key: AIRFLOW-3442
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3442
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: logging
>            Reporter: Dmitry Lukyanchikov
>            Priority: Minor
>             Fix For: 1.10.1
>
>         Attachments: Screen Shot 2018-12-04 at 12.41.50 PM.png
>
>
> When i start to use new RBAC feature with google oauth i notice that owner in 
> audit logs shows as google_[some number]. Its pretty hard to understand how 
> is actually make some changes or run dag. But if there will be first name 
> second name or at least email it will be pretty easy without checking who is 
> using this google_ username. Maybe it can be configured somehow, please advise
> !Screen Shot 2018-12-04 at 12.41.50 PM.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to