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
winsyncMissing: sn $displayName
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
Any RID below 1000 belongs to wellknown SIDs
But I am not sure you can use that to weed out users/groups.
Here you can find a list of SIDs/RIDS that are wellknown:
start at line 200ish
Simo, is this a 6.3 feature? If not, then when?
I don't know, we do not use winsync for our ad trust plans which are the driver for 3.0
(In reply to comment #3)
> I don't know, we do not use winsync for our ad trust plans which are the driver
> for 3.0
So can we mark this as CLOSED WONTFIX?
Would still be a good enhancement until we can completely scrap winsync.
Closing this bug since we moved to the ticket system: