https://bugzilla.redhat.com/show_bug.cgi?id=740081
Description of problem: There are "pseudo-user" accounts in AD that have mostly "user" objectclass schema but are missing required attributes in DS, such as the "sn" attribute. There may be some cases where we want to allow the user to sync these entries: "I think it might be clearer if we synchronized all accounts that do not use built-in SIDs (reserved) and are in the correct cn / ou since there is no such things as a 'psuedo user' in AD. There may be cases where it is desirable for application users to sync, for example a user used for monitoring could log in from an application server to Linux / Windows with the same account. This user might not have all the attributes that a real person would have." We could fill in the missing values in several ways: 1) hard coded value ("Missing Surname") 2) set value to use in winsync agreement entry winsyncMissing: sn Missing Surname or winsyncMissing: sn $displayName or winsyncMissing: sn (objectclass=ipaWinsyncConfig) sn the last is similar to what the ipa-winsync plugin does for missing posix attributes. The list of well-known SIDs/RIDs is found here - http://git.samba.org/?p=samba. git;a=blob;f=librpc/idl/security.idl;h=2b6efc5318480606f19f6fe25976fe9514114fbc ;hb=master
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @rmeggins: - Issue set to the milestone: FUTURE
Metadata Update from @vashirov: - Custom field reviewstatus adjusted to None (was: Needs Review) - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/30
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.