Creating a Site

In EFT, a Site is how you connect to EFT. This topic describes how to create the connection, including IP address, port, and so on.

To create a Site

  1. The Site Setup wizard appears automatically after you complete the Server Setup wizard; otherwise, do one of the following:
    • In the administration interface, click Configuration >Create New Site.
    • Right-click anywhere in EFT's tree, then click Create New Site.

      • The EFT Site Setup Wizard appears.

  2. You are asked to choose the default security level for the Site. If PCI DSS compliance is not a requirement, you can use the default security settings and then manually configure advanced security options individually, as needed. Do one of the following:
  3. Click Next. The Site Label and Listening IP page appears.

  4. In the Site label box, type a distinguishing name for the Site. MySite appears by default, but you can change this to anything you want.

    5. The Site name cannot have a period at the end of the name or use any characters that are not allowed in Windows file naming. The Site label is also used in the Virtual File System (for example, C:\Inetpub\EFTRoot\MySite\Usr) and in logs and reports.

  5. Next to the Listening IPs box, click Configure. The Listening IP Settings dialog box appears.

    • The dialog box displays the IP addresses that are available on the computer, in addition to All Incoming (IPv4) and All Incoming (IPv6).
    • You cannot type in an address.
    • IPv6 is not enabled by default for security reasons; IPv4 is enabled by default.
    • The "All" options are exclusive. That is, you can't select All Incoming (IPv4) and then one or more specific IP addresses. However, you can select multiple individual addresses if none of the "All" options are selected.
    • "Link local" appears next to certain IPv6 addresses. Routers do not forward packets with link-local addresses. In IPv6, link-local addresses are always assigned, automatically or by configuration, and are required for the internal functioning of various protocol components. IPv6 requires operating systems to assign link-local addresses to network interfaces even when routable addresses are also assigned. A link-local unicast address has the prefix fe80::/10 in standard IPv6 CIDR notation.
  6. Select one or more check boxes for the IP addresses on which the Site is to listen for connections, and then click OK. The selected addresses appear in the Listening IPs box.
    • You can copy the addresses in the Listening IPs box: Right-click in the box, click Select All, then right-click again and click Copy or use CTRL+V. (Unicode-related items on the right-click menu are a Windows feature and do not apply to EFT.)
  7. Click Next. The Site Root Folder page appears.

  8. In the Site root box, click Browse to specify the root folder or keep the default displayed in the box. If you type a folder name that does not exist, it will be created.
  9. In the Additional site root folder options area, select the check boxes as needed:
    • Select the Automatically create UNIX-style subfolders check box to create Usr, Pub, Bin, and Incoming folders with appropriate permissions under the Site's root folder. This is only necessary if you are trying to mimic a typical default *nix EFT setup. It is selected by default.
    • Select the Automatically create and assign home folders to newly created users check box to automatically create a user folder under \Site Root\Usr\ when a new user is added. The folder name is the same as the username. For example, username jbite would have the folder C:\InetPub\EFTRoot\MySite\Usr\jbite.

    On an AD-authenticated Site, if Automatically create and assign home folders to newly created users is enabled, EFT creates a virtual folder under the Site's physical root that points to the user's home folders assigned in AD. If Automatically create and assign home folders to newly created users is disabled, the functions for creating virtual or physical folders for AD users are disabled.

  10. Click Next. The User Authentication Provider page appears.

  11. Under Advanced Authentication Options, configure one of the following options (Requires AAMM):
    • None - If you are not using RADIUS, RSA, or Common Access Card (CAC), or SAML (WebSSO)
    • RADIUS - If EFT is connecting to a server using RADIUS, click Configure. The applicable Settings dialog box appears:

      • M

      1. In the RADIUS Server box, provide the name of the RADIUS Server (host name or IP address).
      2. In the RADIUS Server Port box, provide the port the RADIUS Server is bound to. The default port is 1812.
      3. In the NAS Identifier box, provide EFT’s NAS identifier for the RADIUS Server.
      4. In the Shared secret box, provide the shared secret used to encrypt and sign packets between EFT and the RADIUS Server.
      5. In the Connection Retries box, specify the number of times a RADIUS packet will be submitted to the server before giving up. The packet is resubmitted if there is no response from the server. (RADIUS runs over UDP, so packets may be dropped or ignored by the server). The default is 3 retries.
      6. In the Timeout box, specify how long to wait for a server response, in seconds. The default is 3 seconds.

    • RSA SecurID - If EFT is connecting to a server using RADIUS, click Configure. The RSA SecurID Authentication Settings dialog box appears.

      • Click the folder icon to specify the location of the RSA Server configuration file (SDConf.rec), and then click OK.

    • Common Access Card (CAC) - If this Site is using CAC authentication, no further configuration of EFT is required. (Available only on LDAP Sites)

    • SAML (WEb SSO) - If this Site is using SAML (WebSSO), click Configure and provide the details needed to configure SAML, then click OK.

      1. Service Provider:

        • Entity ID - The default is the host name value specified for the EFT Site being configured, e.g., MySite. Any string value can be provided, up 255 characters, including UTF-8 encoded characters.

        • Reserved Path - The base address followed by the SSO path, e.g., [hostaddress]/sp/samlv2/sso.

      2. Identity Provider:

        • Entity ID - The Identity Provider's host name

        • POST URL - The Identity Provider's POST URL or endpoint that EFT should bind to.

        • Public Key - Certificate path to be used for verifying the server's identity

      3. Username:

        • Location in assertion - Specify whether the username is stored as NameID or Attribute.

        • Attribute name - If Attribute is specified for location, provide the Attribute name.

        • Identifier format - Select the list box and click the format identifier from the list:

          • Unspecified

          • Email Address

          • X.509 Subject Name

          • Windows Domain Qualified Name

          • Kerberos Principal Name

          • Entity Identifier

          • URI Reference

          • Basic

    • Turn on "Trace" for SAMLSSO logger in logging.cfg

  12. In the Authentication provider list, specify the type of user authentication this Site is to use. (Click a link below to skip to that section.)

    13. For Globalscape EFT Authentication

    1. Verify that Globalscape EFT Authentication is specified, and then The EFT Server Authentication page appears.

    2. The default path to store the user database appears in the box. If you want to store the user database in a different location, type the path in the box or click the folder icon to find and select or create a folder.

    3. Click Next. The Perimeter Network Security page appears.

    For Windows Active Directory Authentication

    1. EFT is installed by default under the "local system" account, which cannot log in to AD. EFT must be running under an account that has permission to access the domain controller (that is, create a domain account for EFT). Each Site can connect to only one domain. To connect to multiple domains, you must create multiple AD Sites.

    2. In the Authentication type list, click Windows Active Directory Authentication.

    3. Click Next. A prompt appears to remind you that you need to specify a different "Log on as" user for EFT.

    4. Click OK. The Windows Authentication Options page appears.

    5. In the Type area, click Active Directory or NTLM/Local System Accounts to match the authentication method used on EFT's domain. Authentication is done with Microsoft's LogonUser() function in Windows. The operating system then determines which method to use for authentication, such as Kerberos, NTLM2, etc.

      • Active Directory - EFT queries the domain controller for the list of users and groups.

      • NTLM Authentication/Local System Accounts - EFT queries the local system to get the list of users and groups.

        • If EFT is installed in HA mode, you cannot use Local System Accounts.

    6. In the Domain area, do one of the following:

      • Click Default if you want to use the authentication database on the computer's current domain.

      • Click Specify, then in the box, provide the domain name that contains the authentication database.

    7. In the Group area, do one of the following:

      • To allow access to every user in the domain's database, click Everyone.

      • To allow access to only a specific AD Group, click Specify, then in the box, type the AD group name for users that will have access to EFT.

      For information about support for foreign groups, refer to Support for Foreign Groups.

    8. To verify your settings, click Test.

    9. To close the Test dialog box, press ESC.

    10. In the Use this user attribute as the logon name box, click the list to specify the attribute to use (only available when AD authentication is selected):

      • NT 4 Account Name - Username

      • Display Name - (DN) When a new user is created in Active Directory, the Full name field is always generated in FirstName LastName format. This field sets the Display Name field on creation, and you end up with a FirstName LastName formatted global address list.

      • User Principal Name - (UPN) For example, your_user_name@mycompany.com

      • Common Name - (CN) fully qualified domain name, computer name (netbios), localhost

        • Regardless of the logon name chosen, EFT will accept the provided logon name type, whether UPN, NT4 account name, common name, or display name, and if a match exists, the user will be authenticated and the chosen logon name type will be displayed in the administration interface.

        Logon name type

        Allowed login form

        NT4 Account Name (NT4)

        NT4/UPN

        Display Name (DN)

        DN/NT4/UPN

        User Principal Name (UPN)

        UPN/NT4

        Common Name (CN)

        CN/NT4/UPN

    11. In the User list refresh interval box, click the list to select how often you want EFT to check the authentication database for new users (server specified, never, or from 5 minutes to 1 day).

    12. To use AD to authenticate users both in the portal and in the Outlook Add-In using EFT permissions for folder access, select the Access permissions are managed by Windows check box. This property is read-only after the Site is created.

      13. If this check box is NOT selected (disabled/turned off):

      • The VFS subtree in EFT is manageable and works similarly to non-AD-authenticated Sites.

      • The Groups node works similarly to non-AD-authenticated Sites.

      • When the user account log in to the Site (via HTTP/FTP/etc.), EFT uses the credentials (username+password or IWA) to authenticate the client against AD/NTLM, then discards the impersonation token, and all further file/folder operations are done on behalf of EFT's system account, similarly to non-AD-authenticated Sites.

      • Access permission is defined by EFT in VFS.

      • Create a virtual folder and Keep user's home folder check boxes are grayed out in the Site wizard and the Site General tab. These measures prevent clients from getting their EFT home folder mapped to their AD home folder, which most likely does not have access permissions for EFT's system account.

      • EFT does not show the standard "The service may not have adequate permissions depending on your AD configurations" prompt when the administrator starts editing Site authentication manager settings.

      • The authentication manager property is exposed via COM (ICIADAuthManagerSettings interface):

        • HRESULT UseWindowsAccessPermissions([out, retval] VARIANT_BOOL* pVal); HRESULT UseWindowsAccessPermissions([in] VARIANT_BOOL newVal);

    13. Under When creating home folders for newly created users, do one of the following:

      • If you click Create a physical folder, and if NT4 Account Name was selected as logon attribute, you can choose to not include the domain in the folder name by selecting the Don't include domain attribute in folder name, e.g., /jsmith, rather than /domain.jsmith check box.

      • If you click Create a virtual folder, the virtual folder will point to the user's home folder as defined in his/her AD profile. (This option is disabled if Automatically create and assign home folders to newly created users is disabled.)

      • To keep the users' home folders updated based on the AD profile folder for the user, select the Keep user's home folder in sync with AD profile folder check box. Selecting this check box allows AD users that are configured with a home folder in AD to successfully create and share a Workspace.

    14. Skip to configuring Perimeter Network Security.

    For LDAP Authentication

    1. If you are using Common Access Card (CAC) authentication, click Common Access Card (CAC) authentication. (The Configure button applies only to RADIUS and RSA.)

    2. In the Authentication type list, click LDAP Authentication, then click Next. The LDAP Authentication page appears.

    3. In the Server box, type the Server name or IP address.

    4. In the Port box, keep the default port 389 or specify a different port used by your LDAP server.

    5. In the Base DN box, type the base domain name for the LDAP user database, in the format option=value (e.g.: dc=forest,dc=tree,dc=branch), or click List DNs to complete the box automatically or select from a list.

    6. In the User Filter box, type the search filter information. Refer to Advanced LDAP Filtering for a detailed explanation of LDAP filtering.

    7. In the Login Attribute box, type a comma-separated list of attributes to retrieve. Add userprincipalname to the LDAP query so that the userprincipalname is used for the account name in queries. For example, type:

      userprincipalname,mail,email,name,cn

    8. In the Authentication mode area, click one of the following binding methods to define how the client is authenticated:

      • Anonymous

      • Simple requires a username and password. If Active Directory is acting as the LDAP provider, then providing credentials the DOMAIN\username style is sufficient. The credentials provided are typically those of the service account, and the user does not need to have any elevated privileges on the AD domain, only a Domain User. Otherwise, the username must follow the syntax for the LDAP server that includes the Common Name and the Domain Components of your LDAP server’s distinguished name. For example, the username might be the following:

        • cn=Manager,dc=forest,dc=tree,dc=branch

      The LDAP bind password is encrypted in the FTP.cfg file.

    9. If you want to encrypt LDAP communications, select the Bind Using SSL check box.

      10. If Microsoft’s Active Directory is the LDAP provider, Certificate Services must be enabled on the domain before domain controllers will be able to receive encrypted LDAP connections.

    10. Click Advanced. The LDAP Authentication Advanced Options dialog box appears.

    11. Specify advanced options based on your requirements:

      • Set timeout - Specify the connection/query timeout (in seconds). This option coupled with paging can help you avoid timeouts when querying against large directories.

      • Set search scope - This specifies the depth of the level to search for under BaseDN.

        • BASE - Only the requested object specified in BaseDN is searched.

        • OneLevel - All of the objects just below this object are searched.

        • Subtree - Searches for all the objects within the specified BaseDN object recursively.

      • Turn on referral chasing - If you have referral chasing on, the query returns information for objects that exist in the LDAP structure, but do not actually exist on EFT to which you are connected. The query displays bookmarks to entries that exist elsewhere in the network that EFT knows about.

      • Set LDAP Version - LDAP 2 is widely supported and adds anonymous binding and some filtering. LDAP 3 extends the features of LDAP 2 by adding paging (server side) and more complex filtering.

      • Use LDAP server-side page control - Asks EFT to limit result sets (or pages) to 1000 at a time or the value specified under Override search page size, if checked. If Use server page control is not selected, client-side paging is used to mitigate timeouts when retrieving large directory listings.

        • If you are connecting to a SUN Directory LDAP server, turn off page control.

      • Override search page size - Overrides the default page size (1000) for client or server-side page limits. Making the value too large can cause timeouts. Setting the page size too small reduces the overall efficiency.

      • Select attributes - Select the Select attributes check box, then specify the LDAP attributes that you want to use, such as cn (common name), streetAddress, mail (email address), employeeID, employeeType, etc.

        • Multiple attributes can be added to each custom field, but only the first attribute found will be used; All other attributes will be ignored.

        • An attribute field on the LDAP server can contain multiple attributes if you want multiple attributes added to a single custom field, such as for the address.

        • Refer to Map LDAP Account Attributes to EFT User Account Details for more information about LDAP account attributes.

    12. Click OK to close the LDAP Authentication Advanced Options dialog box.

    13. To test your settings, click Test. The Authentication Manager Test Results appear. For details of the LDAP test, refer to Testing LDAP Authentication Settings.

    14. Click the X in the upper right corner to close the dialog box.

    15. Specify the path at which EFT will store additional user settings, if different from the default shown in the wizard.

    16. In the User list refresh interval box, specify the frequency at which EFT's user list should be refreshed. By default, the Server is configured to not refresh automatically.

      17. This setting is disabled on HA nodes; the user list must be synchronized on all nodes at the same time.

    17. Skip to configuring Perimeter Network Security.

    For ODBC Authentication

    1. Click Next. The ODBC Authentication page appears.

    2. In the Specify the data source box, type a connection string for the ODBC database. Refer to Using a DSN-Less Connection with ODBC Authentication for details of creating the connection string, if necessary.

    3. Select the Encrypt user passwords check box to encrypt passwords stored in the database. When this check box is selected, when you create user accounts within EFT, the ODBC database is populated with the username and a SHA-256 hash of the account password. Alternatively, you can set a value in the registry to use MD5 encrypted passwords instead.

    4. In the User list refresh interval list, click the list to specify how often you want EFT to check the database for new users.

      5. You change the refresh interval later in the Authentication Options dialog box.

  13. If you will be using EFT with Azure Data-Lake Storage, next to Override VFS Credentials, click Configure. (You configure it later if you don't have the credentials available.) The Override VFS Credentials dialog box appears.

    1. Select the Enable VFS credentials override check box. The Login and Password boxes become enabled.

    2. Provide the credentials for your Azure Data-Lake supported container and the security key (password), then click OK.

  14. Click Next. The Perimeter Network Security page appears.

  15. Specify whether to connect the Site to DMZ Gateway.

    • If you choose to connect to DMZ Gateway, specify its IP address and port, and then click Test Connection. If the DMZ Gateway is properly configured, the test is successful. If the test is not successful, click I'm not using the DMZ Gateway - or I'll configure it later.

    • If you have not yet installed or configured DMZ Gateway Server, click I'm not using the DMZ Gateway - or I'll configure it later.

  16. Click Next. The Connection Protocols page appears.

  17. Select one or more check boxes for the protocol(s) that this Site will use to connect to EFT and specify the port number for each protocol. The default ports appear in the boxes.

    18. By default, the FTP server in Microsoft IIS binds to port 21 on all IP addresses. If you want to run both the IIS FTP server and EFT, you need to disable socket pooling for the IIS FTP server.

  18. Specify the SSL certificate to use for this Site. Click SSL certs. The SSL Certificate Options page appears.

    • To create a certificate, click Create certificate and follow the prompts in the wizard. (Refer to Creating Certificates for details, if necessary.)

    • To use an existing certificate:

      1. In the Certificate box, type the path to the .crt file or click the folder icon to find and select it.

      2. In the Private key box, type the path to the .key file or click the folder icon to find and select it.

      3. In the Certificate passphrase and Confirm passphrase boxes, type and confirm the passphrase for the certificate pair.

      If you do not enable SSL, you will not be able to connect to EFT from a remote administration interface. Refer to SSL Certificate-Based Login, Creating Certificates and Importing a Certificate into the Trusted Certificate Database for information regarding certificates.

  19. Click Next to return to the Protocols page.

  20. If you are using SSL, click SSL options:

    1. (In v8.0.5 and later) Select the Inherit from server settings check box if you want the Site to use the same configuration, or clear the check box to select different options.

    2. TSLv1.2 is the only version selected by default in v8.0.5. Select other versions and/or ciphers as needed.

  21. Click Next to return to the Protocols page.

  22. (If you are using SFTP) Click SFTP keys to configure an SFTP key pair. The SFTP Keys wizard appears.

  23. Do one of the following:

    • Click the folder to browse for a key, then enter the passphrase.

      • -- or --

    • Click Create to create a new key. The Create SSK2 Public/Private Keypair wizard appears.

      1. Specify a name, location, format, and bit length of the key pair, and then click Next.

      2. Specify and confirm the passphrase to encrypt the private key, and then click Next.

      3. Specify whether to use this key as the default host key and whether to copy the public key to the SSH key manager, and then click Finish.

      4. After the key is generated, click Finish.

  24. You are returned to the Site Setup wizard Protocols page. Click SFTP Security. The SFTP Options page appears.

  25. (In v8.0.5 and later) Select the Inherit options from server settings to use the same configuration as the server, or clear the check box to select different options.

  26. Select the algorithms and ciphers as needed, then click Next.

  27. If you chose AS2, click Configure. The AS2 Setup Wizard appears. Click Next.

    1. Specify Your AS2 identifier. There is no standard for the AS2 Identifier. You can use your name, your company's name, or some other unique name. EFT validates the AS2 identifier to determine whether it is unique (not used by another partner on this EFT). If you type an ID that is not unique, the field resets to blank. Click Next.

    2. Specify the AS2 Certificate public path key, Certificate private key path, and Certificate private key passphrase, populated by default with the SSL certificate paths (if present) for EFT SSL communications. Click the folder icons to specify a certificate pair or click the blue create link to open the SSL certificate wizard to create a new certificate pair. (You can use the same SSL certificate that you are using for the Site.) Click Next.

    3. Click Finish.

  28. Click Next. The Site Setup Completed page appears.

  29. If you specified Globalscape authentication, you are offered the option of running the user creation wizard or quitting the Site Setup wizard and creating users later. Click an option, then click Finish.

    • If you chose Run New User Creation wizard, the User Creation wizard Welcome page appears. Continue to Creating User Accounts for the procedure.

    You can run the Site Setup wizard again at any time to create additional Sites.

    You can view and modify individual Site settings in the administration interface.