Bug 40270

Summary: sync unixHomeDirectory attribute
Product: UCS Reporter: Felix Botner <botner>
Component: S4 ConnectorAssignee: Samba maintainers <samba-maintainers>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P5 CC: gohmann, requate
Version: UCS 4.0Flags: requate: Patch_Available+
Target Milestone: ---   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=32268
https://forge.univention.org/bugzilla/show_bug.cgi?id=49092
What kind of report is it?: Bug Report What type of bug is this?: 2: Improvement: Would be a product improvement
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.046 Enterprise Customer affected?: Yes
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:

Description Felix Botner univentionstaff 2015-12-16 17:13:26 CET
/etc/univention/connector/s4/mapping: user -> post_attributes

'unixHomeDirectory': univention.s4connector.attribute (
          ucs_attribute='unixhome',
          ldap_attribute='homeDirectory',
          con_attribute='unixHomeDirectory',
          single_value=True,
),

Ticket: #2015121121000211
Comment 1 Stefan Gohmann univentionstaff 2016-12-13 08:10:44 CET
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:18:16 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.