For information about Globalscape, visit www.globalscape.com. |
|
|
For information about Globalscape, visit www.globalscape.com. |
|
EFT supports the following database types for authenticating users:
Globalscape Authentication does not rely on outside sources for user information. All information in the database is:
Protected from the operating system
Contained within the .aud file located in EFT installation folder (e.g., C:\Documents and Settings\All Users\Application Data\Globalscape\EFT Enterprise: On Windows 2008, Application Data files for all users are in a hidden folder named %systemroot%\ProgramData instead of under Documents and Settings\All Users\Application Data.)
The path to the .aud file is defined in ftp.cfg. If you change the path to either of those files, you must redefine the path to the .aud file on the Site's General tab User auth manager configuration.
Encrypted and can only be modified through the administration interface.
Windows Active Directory (NTLM/AD) Authentication. Using this method, EFT assigns permissions to users from the NT user database on the system that is running EFT. EFT queries the Primary Domain Controller (PDC) for your domain and adds all domain users to the Settings Template tree.
LDAP (Lightweight Directory Access Protocol) is a protocol for accessing information directories on an LDAP Server.
ODBC Authentication allows all users in an external ODBC database to have access to EFT.
|
Once a Site has been created, you cannot change the authentication method. |
When the High Security module is activated, RADIUS is supported on each Globalscape, LDAP, or ODBC-authentication Site. (RADIUS is available in EFT Enterprise only)
When you create a Site, EFT creates a file called FTP.cfg. FTP.cfg contains a list of all of the users defined on a Site, as well as all of the users' personal information, such as AS2 settings, enabled protocols, e-mail address, home folder, etc. The user lists are organized in the file by Site, so you can have multiple sites with the same account name. Depending on the type of authentication chosen, EFT also creates an .aud file for the Site (e.g., MySite.aud). The .aud file is an authentication database that contains information that is not supported by the chosen authentication method, but is used by EFT. For example, LDAP authentication does not use groups, so the .aud file for LDAP contains the list of groups and distribution of users between these groups that are used in EFT. Active Directory authentication uses the methods and properties provided by the AD server; therefore, EFT does not need an .aud file for AD-authenticated Sites.
