` # Limited access to Samba account attributesĪccess to attr=sambalmpassword,sambantpassword,sambapwdlastset, Include /usr/local/etc/openldap/schema/samba.schema Finally, I moved the Samba account information for my existing users over from tdbsam to LDAP.įor nf, the following lines got added: Then I edited my smb.conf to add the LDAP related directives. After pouring over the doc for awhile I thought I understood what to do, which I did - pretty much.įirst, I added the samba 3 schema file to my OpenLDAP instance’s schema subdirectory and made the necessary changes to my nf (including adding an access control and indexes to support the new objectclass and attributes needed by Samba). With a little time on my hands today, I in fact did take the next step and convert over to the ldapsam backend. Although I’ve tried this in previous installations of both Samba 2 and Samba 3 (while the latter was still in development), my goal this time around was to get the service up and running as quickly and cleanly as possible.
#Export odsee schema via apache directory studio windows
While tdbsam is a good alternative to the older smbpasswd backend that mimics a Windows LSA (Local Security Authority) database, it is understandable that one would assume that eldapo would opt for the LDAP backend.
Someone with an eye for detail might have noticed that the smb.conf I had in an earlier post was configured to use the tdbsam instead of the ldapsam backend.
0 kommentar(er)
