Bug 43447 - Make univention-ad-connector(-exchange) add AD:proxyAddresses into OpenLDAP:mail
Make univention-ad-connector(-exchange) add AD:proxyAddresses into OpenLDAP:mail
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
http://serverfault.com/questions/7242...
:
Depends on: 43216
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-30 17:38 CET by Arvid Requate
Modified: 2019-01-03 07:20 CET (History)
5 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.137
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016121621000432
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 Arvid Requate univentionstaff 2017-01-30 17:38:10 CET
Split off from Bug #43216:

We should adjust the AD-Connector to merge the mail addresses found in the Active Directory "proxyAddresses" attribute into the list of values found in the OpenLDAP "mail" attribute (i.e. attribute sync_mode is fixed to 'read' here). The values found in OpenLDAP must *not* be removed.

This new behaviour should probably be configurable via UCR (e.g. by setting mapping attribute sync_mode = "read+merge").

The test case 55_adconnector/130sync_user_mail_attributes should be extended for this.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:20:38 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.