Configuring access for HTTP host users

Use the HTTP tab to configure access for HTTP host users.

Acceptable inbound files patterns

Specify patterns that files that must match to be permitted inbound. Patterns can include wildcards and regular expressions. See Using wildcards and regular expressions. If specifying multiple file patterns, separate them with semi-colons (;) or commas (,). Alternatively, enter them on separate lines. 

The following are examples of valid patterns:

• * = any file pattern
• *.* = file must have an extension
• *.edi;*.xml = only .edi and .xml extensions acceptable (case sensitive)
• [(?i).*\.(edi|xml)] = only .edi and .xml extensions acceptable (case insensitive)

Users have read-only access

Restricts HTTP users to read-only access of files and directory listings in their home directory. Users with read-only access may only retrieve files or directory listings from their home directory.

Users can overwrite files

Allows files uploaded to this host by HTTP users to overwrite existing files of the same name.  When this option is disabled, existing files of the same filename are not overwritten.  When this option is enabled, existing files of the same filename are overwritten.

Note: This check box is disabled when you select the Users have read-only access option.

Use default file name

Allows the incoming file to be given the name specified in its associated field. Use this option to override the file name specified by the sender. This feature is useful in situations where the received file name must be something other than its original file name. This field can also include any of the supported macros allowing for the incoming file to be named, for example, with a date-time stamp. See Using macro variables (Destination File context) for a discussion of all applicable macros.

Note: This check box and field are automatically disabled when you select the Users have read-only access option.

Users must connect on a secure port

Limits users to SSL connections only. When selected, users will able to successfully authenticate only when an HTTP/s connection is used.

IP filter required

When you select the IP filter required check box, all mailboxes under this host require whitelist IP addresses to be entered. If no whitelist IP addresses are entered for a mailbox, that mailbox is set to “not ready”. If a mailbox has whitelist IP addresses entered, login to the mailbox is allowed only from the IP addresses configured. If a mailbox does not have any whitelist IP addresses entered, the mailbox user can login from anywhere.

If the IP filter required check box is cleared, whitelist IP addresses are not required and mailbox user can log in from anywhere.

Password Policy

Defines the security requirements that will be enforced for all local users.  By default, the Password Policy used by all mailbox users is globally defined using the Enforce Password Policy option on the System Options > Other tab. See Other system options.

To specify a different set of security restrictions for all mailbox users defined for a particular local user host, select the Override System Level Settings option, select the Enforce Password Policy option (if not already selected), click Configure…, make the desired changes and click Apply.  See Configuring password policies for further information about Password Policy options.

To disable Password Policy enforcement for all mailbox users defined for a particular local user host, select the Override System Level Settings option, clear the Enforce Password Policy check box and click Apply.

Associated web portal

Designates the Portal ID of the web portal associated with this HTTP user host.  Select None or a specific Portal ID from the drop-down list.  For information on web portal setup, see Configuring VLPortal Web Browser service.

Portal Applets

If the Portal Applets check box is selected, manual file transfer uses applets to overcome limitations of certain browsers run by users. The Applet transfer limit sets the maximum number of simultaneous transfers an applet session can attempt to use to transfer a set of files and the Users can zip uploads option allows the user to compress the files being uploaded into a single zip file. If Use metadata is selected, then the metadata configured for the portal will be used to prompt the portal user for additional information.  For information on web portal metadata setup, see Configuring manual file transfer metadata.

Users can view transfers for all mailboxes associated at the Trading Partner level

Select this check box to give users the option of including other mailboxes associated with the Trading Partner(s) that the users' mailbox is associated with in the File Transfer History table.