Univention Bugzilla – Bug 46707
Usage of <name> in csv import for schema:displayName
Last modified: 2018-07-04 15:05:04 CEST
Created attachment 9481 [details] import config Set <name> in schema:displayName doesn't work. In schema:email it works great. This make no sense to me. For OX we need a unique displayName and so "<firstname> <lastname>" is not unique in a big environment. For me the best solution is to set the displayName to "<firstname> <lastname> (<name>)". This will be unique. My config and an example import csv is attached.
Created attachment 9482 [details] example csv
(In reply to Tobias Birkefeld from comment #0) > For OX we need a unique displayName and so "<firstname> <lastname>" is not > unique in a big environment. For me the best solution is to set the > displayName to "<firstname> <lastname> (<name>)". This will be unique. For OX you need a unique "oxDisplayName". The "displayName" attribute does not have to be unique.
Created attachment 9483 [details] import config
The root cause is this: Bug #42137. In this specific case the reason is: def prepare_all(self, new_user=False): self.prepare_uids() self.prepare_udm_properties() self.prepare_attributes(new_user) Both "oxDisplayName" and "displayName" are formatted in prepare_udm_properties(), while "name" is formatted in prepare_attributes().
username(In reply to Sönke Schwardt-Krummrich from comment #2) > For OX you need a unique "oxDisplayName". The "displayName" attribute does > not have to be unique. That's right, but also for oxDisplayName you can't use <name> or <username> like in ucs user templates.
*** This bug has been marked as a duplicate of bug 46754 ***
Yes, it's a duplicate.