James Meickle created AIRFLOW-3535:
--------------------------------------
Summary: Airflow should collect display names, not Firstname /
Lastname
Key: AIRFLOW-3535
URL: https://issues.apache.org/jira/browse/AIRFLOW-3535
Project: Apache Airflow
Issue Type: Improvement
Components: database, ui
Affects Versions: 1.10.1
Reporter: James Meickle
We use Google OAuth to provision our Airflow accounts. This creates "user
names" of "google_12345", with the corresponding email address. The first and
last name of the user are pulled into the corresponding Airflow fields.
In general, though, First Name / Last Name is not considered a good pattern for
user systems unless they are actually critical to handle business logic.
Further reading on problems that can cause here:
https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
We should condense these fields into a totally freeform "Display Name", and use
that more consistently in the UI. For example, in AIRFLOW-3442, an internal
username is displayed rather than a display name. (In the case of an audit log,
the right value is probably: `Display Name (internal_name)`.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
