Bug 45997 - Remove "email" scheme from default config
Remove "email" scheme from default config
Status: CLOSED DUPLICATE of bug 45972
Product: UCS@school
Classification: Unclassified
Component: Import scripts
UCS@school 4.2
Other other
: P5 normal (vote)
: ---
Assigned To: Daniel Tröder
Sönke Schwardt-Krummrich
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-10 12:34 CET by Michael Grandjean
Modified: 2023-03-25 06:55 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2018-01-10 12:34:39 CET
Currently we have an email scheme defined in the default configs:

> /usr/share/ucs-school-import/configs/user_import_defaults.json:         "email": "<firstname>[0].<lastname>@<maildomain>",
> /usr/share/ucs-school-import/configs/user_import_http-api.json:         "email": "<firstname>.<lastname>@<maildomain>",

This is a problem when we explicitly do NOT want mailPrimaryAdress to be set during import, because it cannot be overwritten. As discussed with Daniel, I tried the following variants:

"email": "",
"email": null,
"email": none,
"email": false,

in my local user_import.json, but they all produce tracebacks.

IMHO we should just remove the "email" scheme from the default configs and make it necessary to specify one in the local config, if needed. In this case, we should also check for side effects, e.g. "recordUID": "<email>"
Comment 1 Daniel Tröder univentionstaff 2018-01-11 10:29:04 CET
Will be fixed as part of Bug #45972.

*** This bug has been marked as a duplicate of bug 45972 ***