LDAP home folders

You can define entries in the Home Folder page that SecureTransport uses to set the home folder ( fdxHomeDir attribute) for an LDAP user when the attribute is not set by the other actions listed in LDAP logins. If there is an entry for the user's user class or for all users, SecureTransport uses the configured prefix. For example, if the prefix is /home/users/partners and the user name is suplco, SecureTransport set the home folder to /home/users/partners/suplco.

When SecureTransport is running under Windows, you can use a local file path, such as D:\home\users\partners or a UNC path for a share such as \\NAS2\home\users\partners. The permissions for the share must permit the SecureTransport Administration Tool service, which runs on Windows with a local system user as its owner, to create the folder. If the permissions granted for the share are not sufficient to create the subfolder for the LDAP user’s home folder, SecureTransport refuses the connection.

Note Because operating systems do not accept angle brackets ( < >) and quotation marks ( ") in file names, LDAP users with any of those characters in their user name cannot log in to SecureTransport and get a default home directory. You must map such users to a properly configured account template.

You can define a user class based on values from the LDAP entry. See User classes.

If there is no entry for the user class, SecureTransport uses the entry for all users indicated by an asterisk ( *) in the User Class field.

For more information about how SecureTransport uses the entries on the Home Folder page during LDAP logins, see LDAP logins In particular, if there is an applicable account template, the home folder defined in the account template replaces any home folder set from configuration on the Home Folders page.

The following topics describe managing LDAP home folders:

Related Links