Standard browser client

You can use a standard browser, such as Firefox or Microsoft Internet Explorer (IE) to connect to a SecureTransport Server. Using a browser allows easy access to the SecureTransport Server, but it does not offer all the features of Axway Secure Client applications. For example, the browser client does not support the Automatic Restart function. Browsers connecting to SecureTransport must support JavaScript.

No additional configuration is required on the server side for users to connect to the server with a standard browser. You can customize the interface if you prefer.

Note Customization of the interface requires knowledge of HTML and JavaScript.

The client must have JavaScript and cookies enabled.

Customize a web client

To create a custom browser client, copy the files for an existing browser HTML template and modify them. You must make the changes on all servers in a cluster.

Customize the browser client interface

The pages for the SecureTransport default browser client interface are created from HTML template pages. There are template pages for each locale supported by the server. The pages are located in the <FILEDRIVEHOME>/share/ftdocs/html/<Locale> directory, where <Locale> is the supported locale. The default pages are in the C (for English) directory.

Note Additional template pages reside in <FILEDRIVEHOME>/share/ftdocs/html/skin/jb9 and <FILEDRIVEHOME>/share/ftdocs/html/skin/sm6. A <Locale> subdirectory contains the HTML files for each additional template. For more information about setting the HTML template used for the browser client, see Select a default HTML template.

The pages include embedded macro strings. A macro string is a special string in HTML which the SecureTransport Server understands and replaces with HTML or JavaScript code. A macro string is enclosed in angle brackets and two dashes and includes an exclamation point. For example:


To customize the browser client interface, edit the HTML template pages. All custom pages must include the appropriate macro strings as listed in the Macro Strings table. Most of the HTML in the templates can be changed. The JavaScript functions can also be changed. Make these changes on each node of the cluster where they are required.

Note Editing or creating a JavaScript function must be defined in the template page.

Do not change the following parameters while editing the templates:

  • Name/Value in any of the forms
  • These are hardcoded in the server.
  • URLs for listing, downloading, and deleting files. Do not define new macro strings or change the definition of existing macro strings.

The browser interface has template pages for the following functions:

  • Login and logout
  • List
  • Download
  • Session timeout
  • Options
  • Account and password management
  • Message

Macro strings

The following table provides information on the macro strings that are supported by SecureTransport. Some macro strings are only supported in specific template pages, as indicated in the Description column.

Macro string Replaced with: Description
FDX_CHANGE_PASSWORD_MSGS The policy used in changing passwords. It is replaced by one of four FDX Messages (see FDX_MESSAGE). Used only on the Change Passwords page.
FDX_CLICK_URL /~ Specifies the relative URL to which the user is redirected after displaying the authentication message, for example if the AuthMessage parameter of AuthAgent is set to "Yes".

For every file or directory present in the current directory, SecureTransport adds the following line:

("FileURL", "FileName", "isDir", "size", "date", "icon")

FileURL – the name of the file which can be used as the URL

FileName – the name of file

isDir0 for directory or 1 for a file

size – size of the file (for a directory, size is N/A), date is the modification date of a file

icon – the URL of an image file to be used as icon

Used on the List page only.

FDX_FILE_NAME The current file or directory name. Used in the List and Options pages.
FDX_FILE_URL The escaped file name, which can be used as a URL. Used in the List and Options pages.
FDX_HIDDEN_START_URL <input type="hidden" name="start-url" value="/myfile.txt"> Specifies the original URL that an unauthenticated user attempted to access. Upon successful login, the user is redirected to this URL.
FDX_LIST_PARENT_DIR The directory hierarchy of the current directory.

This is an alternative to FDX_PARENT_DIR_FUNC, which displays the directory structure as it is displayed in the default template.

Used on the List page only.

FDX_MESSAGE FDX_Msg("message")

message – the message to be displayed

Used on the Login, Password Fail, and Password Success pages.

FDX_OPTIONS_PARENT_DIR The directory structure of the current directory.

An alternative to FDX_PARENT_DIR_FUNC, which displays the directory structure as it is displayed in the default template.

Used only on the Options page.

("DirName", "DirURL")

DirName – the name of parent directory.

DirURL – the name of parent directory which is sent as a URL. This string is an alternative to FDX_LIST_PARENT_DIR, which can be edited.

Used in the List and Options pages.

FDX_PASSWORD_PRINT_FORM PrintForm() Used on the Password Success page only when the server needs to include the login form.
FDX_SERVER_INFO PrintServerInfo(
"name", "version", "build", "host")

Server version information:

name – the name of the server

version – the version of the server

build – the build number of server, always 0

host – the host name of the server computer.

Used only on Login page.

FDX_XFER_MODE PrintXferMode(mode)

mode – the transfer mode: 1 for binary or 0 for ASCII

Used on the List page only.

Customize the browser client login

You can customize the type of login page the browser displays for browser client users. Change the values of the parameters described in the following table in the Server Configuration page. After you change any of these parameters, bounce the server.

Parameter Use

Controls what type of login the server displays to browser client users. Valid values are:

BA – The server displays a basic authentication window for the user to type their name and password.

HTML – The server displays an HTML page for the user to type their name and password.

ERR – This is used for special cases, for example where cookies are used for authentication. When ERR is set, an authentication request does not occur. To get an authentication request, enable auth, and config agents.

PREAUTH – Enable auth and config agents. If authorization fails, the server displays an HTML page for the user to type their name and password.

Note When PREAUTH is set for Http.FdxAuthReply, SecureTransport uses *nobody as an internal constant value indicating that no user is authenticated with internal agents. If a user with the name *nobody already exists on the operating system, this may cause a conflict that prevents that user from logging in.
Http.FdxAuthAliases This parameter controls whether items in the <FILEDRIVEHOME>/share/ftdocs/icons/ and <FILEDRIVEHOME>/share/ftdocs/html/ directories are authenticated. Set it to OFF to display custom icons on the login page.

Remove the server information displayed on the login screen

To remove the display of server information in the SecureTransport browser client, you must modify the <FILEDRIVEHOME>/share/ftdocs/html/C/login.html file.

Modify the function PrintServerInfo to return 0 as shown in the following code:

function PrintServerInfo(name, ver, build, host) {
    return 0;




Related Links