AD Auth for FTP on 8.3.0 ?

Status
Not open for further replies.

jakeharrop

Cadet
Joined
Nov 1, 2012
Messages
2
Hi,

just upgraded (clean install) from 0.7.2 and finally got round to doing AD auth. Managed to bind to AD and wbinfo -u and -g show all the correct users and groups, but none show within the freenas users or groups GUI. I CAN access CIFS shares ok with domain credentials (well, it doesn't actually ask me for any when I access from my domained PC, so I'm assuming it's working ok).

I'm hitting problems with FTP though. The FTP ZFS volume has domain users set as owner (group), and associated full read, write and execute permissions, and the FTP service has the correct path to the volume set, but when I try and access the FTP site, I see the following error in the logs:

Nov 1 12:45:46 freenas proftpd[7044]: 127.0.0.1 (192.168.25.22[192.168.25.22]) - jake chdir("/home/MYDOMAIN/jake"): No such file or directory

Now, in some ways that doesn't surprise me, because as far as freenas is concerned, I don't exist other than as an object in AD. Because freenas doesn't seem to sync user accounts from AD, I don't have a home folder and never will (although at least it looks like it's authorising me via AD). If I set up a local account and set my home folder as the FTP volume, everything works, but I want to auth FTP from AD so this is a no-go.

If I tick the 'Always Chroot' box in FTP I get a slightly different error:

Nov 1 12:58:17 freenas proftpd[7440]: 127.0.0.1 (192.168.25.22[192.168.25.22]) - notice: unable to use '~/' [resolved to '/home/MYDOMAIN/jake/']: No such file or directory
Nov 1 12:58:17 freenas proftpd[7440]: 127.0.0.1 (192.168.25.22[192.168.25.22]) - chroot to '~/' failed for user 'jake': Operation not permitted
Nov 1 12:58:17 freenas proftpd[7440]: 127.0.0.1 (192.168.25.22[192.168.25.22]) - error: unable to set default root director


Anyone got any ideas ?

Thanks

Jake
 

henry_k

Cadet
Joined
Nov 3, 2012
Messages
1
Hi,
there seems to be a bug in the GUI, had the same problem. The "Path" field does not seem to have any effect. A workaround is to click on the "Advanced Mode" button and adding:
DefaultRoot /mnt/whatever
in the auxilary parameters field. Another thing i ran into is that the directory permission "write" for the group account that you select in the ZFS Datasheetsis not applied and has to be set manually via the CLI (eg. chmod 775 <directory>)

Cheers
Henry
 
Status
Not open for further replies.
Top