You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the objects registration admin this works as expected (ie. first time login results in a readable user name; this should be how it works in de objecttypes admin).
The text was updated successfully, but these errors were encountered:
This is a configuration aspect in the OIDC configuration as far as I know. The OIDC protocol prescribes that unique identifiers have to be used, which is done here. If your organization can guarantee that another claim is also unique, it should be possible to specify this claim as username source instead, I think.
No, in mozilla_django_oidc_db version 0.6.0 you can't configure the username claim (stupidly enough?). It is always the "sub" key. Solution: bump objecttypes to latest version which has mozilla_django_oidc_db version 0.7.2 which allows for a custom username claim.
first time login gives


in the backend:
The username TdM08... should be my name.
In the objects registration admin this works as expected (ie. first time login results in a readable user name; this should be how it works in de objecttypes admin).
The text was updated successfully, but these errors were encountered: