Bug 49007 - Add employeeNumber to AD Connector mapping
Summary: Add employeeNumber to AD Connector mapping
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: AD Connector
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: Samba maintainers
QA Contact: Samba maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-15 12:36 CET by Valentin Heidelberger
Modified: 2024-06-27 12:10 CEST (History)
0 users

See Also:
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?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID: 00006
Max CVSS v3 score:
heidelberger: Patch_Available+

Attachments
Patch that adds a mapping for the attribute employeeNumber to AD Connector mapping (567 bytes, patch)
2019-03-15 12:36 CET, Valentin Heidelberger 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Heidelberger univentionstaff 2019-03-15 12:36:47 CET 
Created attachment 9929 [details]
Patch that adds a mapping for the attribute employeeNumber to AD Connector mapping

A customer wanted to have the LDAP attribute employeeNumber synchronized to an attribute of the same name in AD and S4. I think it makes sense to integrate the resulting patch into the default mapping.
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:42 CEST 
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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