What's coming in 7.7
-
@girish about this point: "oidc/ldap: fix display name parsing to send anything after first name as the last name" ... I think logic has to be analyzed again... because is not working as described. Eg. "Willem van Oranje", after this update, becomes "Willem Oranje"... ("Van" is lost)
-
@p44 yeah ,I think for that to be done correctly we have to take first name/last name as proper separate fields. Current logic is too simplistic.
-
@girish this was noticed and discussed more than a year ago … https://forum.cloudron.io/topic/8345/cloudron-ldap-middle-name-not-correctly-propagated
-
@imc67 @p44 so, in 7.7 atleast, we did something like this:
+ const names = [ + { in: 'James', out: { firstName: 'James', lastName: '', middleName: '' } }, + { in: 'James Anderson', out: { firstName: 'James', lastName: 'Anderson', middleName: '' } }, + { in: 'James Philip Anderson', out: { firstName: 'James', lastName: 'Philip Anderson', middleName: '' } }, + ];
So,
Willem van Oranje
would be parsed as firstNameWillem
and lastNamevan Oranje
. While not correct , atleast all the parts of the name are delivered to the app. Pre 7.7, parts of the name were dropped. I am wondering why app uses middlename now. What app are you testing with ? -
In Grafana, my names shows correctly, for example:
Note that it could also be that the app in question is not updating the name on OIDC re-login.
-
Only persons with a double first name it becomes:
Marie Therese van der Steen tot Oberndorff
First name: Marie
Lastname: Therese van der Steen tot Oberndorff -
G girish unpinned this topic on
-
G girish locked this topic on