53 Commits

Author	SHA1	Message	Date
Andrew Tridgell	fe3294f7f0	r2803: allow unixuid module to work with foreign security principles ... (This used to be commit f522728728fa523ce7d9e73c93b27e71f3757d50)	2007-10-10 12:59:35 -05:00
Andrew Tridgell	c5722fb81b	r2796: - changed ldap attributes "UnixID" to "unixID" and "UnixName" to "unixName" to be more ldap traditional ... - register the unixuid module as all 3 ntvfs backend types, as it doesn't care what type of backend it filters (This used to be commit cd43def6ce280442306f14ca61508b4f7eb92cb6)	2007-10-10 12:59:34 -05:00
Andrew Tridgell	5a872512b0	r2794: a very simple version of the unixuid NTVFS pass-thru module. In ... conjunction with the posix backend this gives us a way to correctly setup the unix security context in Samba4. I chose the following method to determine the unix uid's and gid's to use given the list of SIDs from the login process - look for a "UnixID" field in the sam record. If present, then use it (check if the record is of the right type as well) - if UnixID is not present, then look for the "UnixName" sam field. If it is present then use getpwnam() or getgrnam() to find the unix id. - if UnixID and UnixName are not present, then look for a unix account of the right type called by the same name as the sAMAccountName field. - if none of the above work then fail the operation with NT_STATUS_ACCESS_DENIED obviously these steps only work well with a local SAM. It will need to be more sophisticated in future. I did not put any cache in place at all. That will need to be added for decent performance. (This used to be commit 78b67d19b9766131f0270e451089ee5bb1aa8bd9)	2007-10-10 12:59:34 -05:00