Ebase Secure Forms

Documentation home

Configuring Ebase Server

Using Ebase Secure Forms

Ebase secure forms enable a secure/encrypted HTTPS connection between the client and the Ebase Server. Secure forms are activated using Ebase Designer.

When a form is secure it cannot be viewed using the HTTP protocol. The format of the URL is as follows:

https://www.yourdomain.com/ufs/ufsmain?formid=CUSTOMER_DETAILS

If a form is secure and a client tries to access a form using http, the link is automatically forwarded to a secure link (https). Unsecured forms can be viewed as https if SSL is enabled through the application server configuration.

Note: The application server must be configured to accept https connections before enabling Ebase secure forms. If the application server is not already configured to accept https connections, please refer your application server documentation to configure https before proceeding.

Configuring Ebase Server

If the application server SSL port is not configured to listen on port 443, then you must edit the UFSSetup.properties file.

Open the file and add/edit the values:

#Secure Socket Configuration

Ufs.secureSocket=8443

If the property Ufs.secureSocket does not exist then port 443 will be assumed as default.

The server will restart itself if this file is modified.

Using Ebase Secure Forms

Secure forms can be enabled from the form properties dialog box located on the form toolbar.

Select the ‘Yes’ radio button located next to ‘Secure Form:’

Click OK button and run the form.

When the page loads it will automatically be redirected to the secure HTTPS connection. You should see that the URL now shows as:

https://www.yourdomain.com/ufs/ufsmain?formid=CUSTOMER_DETAILS

Also note that with Internet Explorer, a padlock icon is displayed at the bottom of the browser window illustrating that this is a secure connection: