Label |
Mandatory |
Description |
Default Page |
Yes |
Path to the main page for the Portal where applicable authentication methods are listed. Enter path without protocol. Example: /index.html Set to default.html by default. |
Welcome Page |
Yes |
Path to the Portal or page configured as start page after a successful logon. Enter path without protocol. Example: /index.html Set to /wa/desktop.html by default. |
You can perform Device Control using Device Settings and Device restrictions.
Devices are registered as Device Definitions (in the section Device Definitions in the left-hand menu), where you define the kind of devices you wish to control. Note that devices can be specific applications, tokens, or operating systems.
In order for Digital Access to recognize devices other than Web browsers to be able to provide the applicable graphical user interface, you use the Device Setting File Extension.
When using File Extensions, each template (error page, authentication page etc) has both a HTML and a WML version, providing two different GUIs to display the same contents and functionality. You can configure an arbitrary number of file extensions to an arbitrary number of devices.
Additionally there is support for different PDA screen sizes without having to specify a file extension for each screen size. To achieve this, the setting GUI Constant can be used to specify a text that can be inserted into the GUI.
For example, an HTML page or a style sheet may include a company logo image. Instead of hard coding the image name, it can be inserted as <img src=”/img/[$screen-resolution]/companylogo.gif” />. If the GUI is designed like this, all devices accessing the GUI may provide different values of the GUI constant "screen-resolution". Different devices will then get different sizes of the logo image even though all use the same HTML files (all that end with .pda.html).
In this example we have three versions of company logo:
/img/320x200/companylogo.gif
/img/200x200/companylogo.gif
/img/800x600/companylogo.gif
With a style sheet or HTML page referring to “/img/[$screen-resolution]/companylogo.gif”.
Then we add three device definitions (in the section Device Definitions in the left-hand menu), all recognizing the specific screen resolution by looking in the HTTP headers.
Finally, three Device Settings are specified. One for each new Device Definition. On each device setting we specify the GUI Constant "screen-resolution" with the values “320x200”, “200x200”, and “800x600” respectively.
When the page is generated to client, the proper image for the device is loaded.
Please note that the default configuration does not take advantage of GUI Constants.
You can specify the level of control for clients or applications connecting to the Access Point using device access restrictions. You can for example warn users using a certain browser, or disallow others to enter.
Device access restrictions are controlled in the order they are listed. On first match, the restriction takes effect independent of it is a Deny, Warn or Accept restriction.