OES2 Linux natively integrates existing Linux services with eDirectory, so network administrators don’t have to manage multiple identities separately for each service.
One good example is the Pure-Ftpd service. By installing the package Novell FTP during the OES2 Linux install, the Pure-Ftpd is automatically configured to authenticate users against eDirectory.
However, if you need to setup your server as an authenticated FTP server (not anonymous login), pure-ftp does not have a specific configuration to set a common ftp root directory for the whole system. Users always get into their home directories when they log in to the pure-ftp server.
On this customer specific scenario, they have a system that relies on the FTP service. The system authenticates against the FTP server using three different users, which should read and write to the same directory. They need to use different users so they can track who modify/create/delete files.
To accomplish this, we setup these user’s home directory to point to a common location in their LUM configuration:
- Setup a common directory to share files:
In this example we create the /srv/ftp/common directory.
And give the needed access on the directory:
chmod 771 /srv/ftp/common*Note – In this case we give a posix permission to a standard Linux directory but it could be a NSS volume mount point. The trustees could be configurated using the Files and Folders plugin within iManager. NSS trustees assignments do have effect on directories accessed via ftp.
- Using iManager, select Modify to change the user’s settings, under the Users menu.
Figure 1 – Selecting the user to be edited
- Change the home directory for the user within the Linux Profile tab. Point the location you setup above.
Figure 2 – Changing the home directory
- Repeat steps 2 and 3 for all the users you need. Always point the home directory to /srv/ftp/common.
- You are done!
This document assume that you have already setup these users as Linux enabled.
LUM and pure-ftpd are working properly.
This configuration will also affect other Linux-enabled applications/access, for example SSH.
This configuration will NOT affect the user home directory access via a standard NCP connection (Novell Client). Users will keep accessing their home directories (if configured) independently.