There is a useful description of the problem in this document.

We plan to tackle this by implementing OIDC authentication in T353794

By doing this we will be able to retrieve additional information from the authentication system and use it to populate the additional database fields.
For reference, this is where we do a similar thing with DataHub: https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/954132/16/charts/datahub/charts/datahub-frontend/values.yaml

When authenticating, we can retrieve the preferred_username and email values, as well as a list of groups of which the user is a member.

This should allow us to populate the First Name, Last Name, and email fields automatically, which will improve the user experience.

In addition to that, we can assign additional roles based on group membership, which will ease administration and upgrades.
Currently we assign a WMF Analyst role to all users and we have to update this role with new permissions every time we deploy a Superset upgrade.

Change 1006547 had a related patch set uploaded (by Brouberol; author: Brouberol):

[operations/deployment-charts@master] superset: assign Superset roles from LDAP groups

https://gerrit.wikimedia.org/r/1006547

Change 1006547 merged by Brouberol:

[operations/deployment-charts@master] superset: assign Superset roles from LDAP groups

https://gerrit.wikimedia.org/r/1006547

This was fixed in https://gerrit.wikimedia.org/r/1006547, where some custom OIDC login code makes sure to update the Superset User record with the data sent back by the OIDC server.