ARADIAL TECHNOLOGIES Aradial Enforcer Manual Version 7.0

Transcription

1 ARADIAL TECHNOLOGIES Aradial Enforcer Manual Version 7.0 Administration Guide

2 A R A D I A L E N F O R C E R Administration Guide

3 Aradial Technologies Ltd. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without a prior express written permission from Aradial Technologies Ltd. All other products are trademarks or registered trademarks of their respective owners.

4 Table of Contents INTRODUCING ARADIAL... 5 BEFORE YOU BEGIN... 5 CONVENTIONS... 6 USER MANAGEMENT METERING... 7 MAC AUTHENTICATION... 8 PREPAID CARDS... 9 CARD TYPES GENERATE PREPAID CARDS GENERATE SINGLE PREPAID CARD MANAGE PREPAID CARDS PREPAID CARDS REPORTS CARD SESSION SUMMARY TIERED ADMIN ACCESS WEB SELF CARE USER SUMMARY UPDATE USER CHANGE PASSWORD VIEW SESSIONS WIFI / HOTSPOT PORTAL... 33

5 Chapter 1 Introducing Aradial Welcome to the Aradial Enforcer Solution. Aradial Enforcer is based on the Aradial AAA server and adds the following functionalities to it: 1. Quota management both time and volume quotas. 2. Prepaid card management. 3. Self service portal 4. Captive portal for Wifi access This manual describes the Aradial Enforcer additional functionalities and it complements the material on the Aradial AAA manual. Before You Begin This manual is intended for both first time and experienced Aradial users. If you are a first time user, please take time to read this manual from its beginning to its end, before actually putting into practice the procedures it describes. This will aid you in understanding the logic of Aradial and using Aradial to its full potential. Not doing so might cause undoing and redoing some procedures just because you might find in each chapter better and faster ways of putting your thoughts and needs into practice. If you are an experienced Aradial user, you may use this manual as a reference guide when configuring your system. Please notice that a lot of work has been put into Aradial and this manual, yet in some cases the manual might prove outdated, just because it was printed or added to the distribution CD before some new features have been added to Aradial. If you encounter new features or changes in Aradial which are missing from this manual, please refer to Aradial Internet web site at which will always include all latest information regarding Aradial, whether it is new features, updates to the software, or new information regarding vendors supporting RADIUS (hence supported by Aradial). 5

6 If you still have questions after reading this manual, and you are not able to find the information in our Internet web site. Please contact us by: Conventions C O N V E N T I O N S Type Italic Valuable information You should keep this information in mind when performing the related procedure. Required step Make sure you have done this when performing the related procedure. Type in You should type in the information as described in the procedure Placeholder Indicates a placeholder for information parameters you must provide. For example, if the procedure requires you to type NAS, you need to enter the actual name of the NAS. The conventions on the left are used throughout this manual to emphasize essential information. These conventions will help you understand how the information is valuable to you. Paying attention to these conventions will save you precious time by pointing out the essential information, without which, your setup might not work properly. 6

7 Chapter 2 User Management Metering The metering feature in the Aradial Enforcer allows you to control the usage of the user, the usage can be limited either with time or volume. Once the user has exceeded his permitted usage, he will not be able to log in until he renews his Meter Bank. Meter Bank Time this field holds the maximum time the user would be allowed to surf. When this time is depleted the user will not be able to login again. Note: The time that is returned to the NAS is calculated according to the minimum between TimeBank and the time to expiration. Note: The Time Bank and expiration are overriding the Session-timeout in the group. Data - this field holds the maximum traffic for upload and downloads the user would be allowed to surf. When this bank is depleted the user will not be able to login again. Enforce Time and Traffic check boxes if to enforce the banks. Note: certain routers support traffic limit within a session, like Mikrotik, Chillispot, Nomadix, Colubris and others. In such cases Aradial will send the traffic limit to the router that would disconnect the users close to the breaching of the traffic limit. The configuration/script is in the Metering.tcl script. 7

8 Chapter 3 MAC Authentication MAC authentication is a special authentication performed by the access-controller (NAS) before the normal portal based authentication. It uses the MAC address of the user s device as the user-name. Its aim is to bypass the portal authentication which requires the user to enter its user-name and password. Aradial RADIUS server detects a MAC authentication and treats it differently from a regular authentication, as follows: 1. The user is identified by its caller Id field, rather than the User Id. 2. Password verification is disabled. For binding the user to a specific MAC address and automatically setting its MAC address (Caller Id) as the first one the user uses, enable Auto Add Caller Id in the user s Group: Auto Add Caller Id Once set, the Caller Id field of the user will be set upon the first authentication of the user with the Caller-Id value of the authentication. 8

9 Chapter 4 Prepaid Cards Aradial supports unlimited card / user types and allows operators to generate massive bulks of prepaid cards or users. The following features are supported by Aradial prepaid cards: Unlimited numbers of card types Card types management (add, edit, remove) Generate prepaid card batches Generate single prepaid card Full batches life cycle management Manage prepaid card batches Prepaid cards summary and detailed reports Card sessions summary 9

10 Card Types The Card type page can be found under Aradial main page Prepaid Cards Card Types option. The card types allow the operator to define a set of prepaid card templates, which allow easy batch generation later on. The card type entity support a set of definitions at the card level. Adding Card Type page: Card Type: a free text field which allows setting the card type name. The card type will be used once generating batches of prepaid cards and actually enables a segmentation capability for prepaid cards. Time Bank: holds the number of seconds at the card type level. When generating prepaid cards batch using a specific card type, the related value in the time bank will be used for the generated cards and will be enforced by Aradial. Predefined values can be selected from the drop down however, you are allowed to fill any free value by choosing the "other" option. Traffic Bank: holds the number of MB at the card type level. When generating prepaid cards batch using a specific card type, the related value in the traffic bank will be used for the generated cards and will be enforced by Aradial. Predefined values can be selected from the drop down however, you are allowed to fill any free value by choosing the "other" option. Card Length: specifies the card ID length. Password Length: specifies the card password length. Password Symbols Set: a combo box which allows the user to set the password symbols. The possible values are: Alpha numeric, digits only, capital and numbers, alpha numeric readable and custom which allows the user to define and customize rules in Aradial configuration. Enable Password: selects whether the generated cards will have a password (Yes) or will not have a password (No). In case of no password, the cards will have a password source of No Password. 10

11 User Name Type: decides whether to create the user names / card ID in sequential order or random order. Card Price: Set the card price. When generating the prepaid cards, the user will be able to choose a price from a predefined list or set his own price by choosing the 'other' option. Group Name: defines the group name to be associated with the created users at the card type level. Business entity: allows a business entity association. Choosing a business entity means that all created cards will be registered under the chosen business entity. Edit Card Type page The edit page displays all existing card types and allows opening and editing certain details. Card Type: the card type name. Clicking on the card type will open the selected card type in edit mode and allow changes. Time Bank: the value for the time bank Traffic Bank: the value for the traffic bank Card Length: the value for the card length Password Length: the value for the password length Price: the value for the card price Default Group Name: the value for the selected group name Business Entity: the value for the card business entity (or None if no business entity was selected) 11

12 Generate Prepaid Cards The Generate prepaid cards page allows the user to generate batch of prepaid cards or adding prepaid cards to an existing batch using predefined card types or by creating new prepaid cards. The user has full control over the batch parameters and input values which allows high flexibility. Card Type: allows creating a batch of prepaid card using predefined card types. The combo box will present the available card types. When selecting a specific card type, the related attributes will automatically be populated. The Card type is not mandatory and the user may generate a batch using his own parameters and not using the predefined card type. For such cases, the user will be requested to fill in all input parameters for the prepaid card generation. 12

13 Number of Prepaid Cards to Generate: specifies the number of cards to be created. Enable Password: selects whether the generated cards will have a password (Yes) or will not have a password (No). In case of no password, the cards will have a password source of No Password. Batch Prefix: selects the prefix to be used for the generated cards. The same prefix will be used for all created cards. Cards Batch: specifies the batch to which the cards will be assigned. You have an option to generate prepaid cards with an existing batch by selecting a batch from the combo box field, which presents the available batches in the system. For a new batch you should use the 'None' value and fill in a new batch name. Number of Seconds: number of seconds to be included in the cards time bank. You can select a value from a predefined combo box and also specify any other value by selecting the 'other' option and specifying the value. Number of Megabytes: number of MB to be included in the cards traffic bank. You can select a value from a predefined combo box and also specify any other value by selecting the 'other' option and specifying the value. Card Number Size: the size of the generated card. This is also the user ID which will be used for the user authentication. Expiration Date: allows setting an expiration date for the cards. Blank value means no expiration date. Status: weather to create the cards as active (and ready for use), prospective or suspended. Active cards are ready for use while non-active cards require manual activation (please refer to the Manage section). Password Symbols Set: a combo box which enables to set the password symbols. The possible values are: Alpha numeric, digits only, capital and numbers, alpha numeric readable and custom which allows to define and customize rules in Aradial configuration. User Name Type: decides whether to create the card ID in a sequential order or a random order. Start Number in Range to Generate: the field specifies the start number to be used after the batch prefix. For example: batch prefix A with start number and card length 6 will generate the following cards: A10000, A10001, etc Card Price: specifies the card price. Will be filled automatically when using a predefined card type. Password Size: specifies the password size to create for the cards. Group to Assign: specifies the group the cards will be created under. Business Entity: specifies the business entity the cards will be created under. Return Detailed Results: checking this flag means that the generated prepaid cards will be presented on the screen after the operation is completed. 13

14 Export to File: checking this flag means that the generated prepaid cards will be exported into a CSV file after the operation is completed. The following screenshot present a batch using a predefined card type where part of the fields are automatically set and disabled: Once populating the cards details and pressing on the 'Generate' button, the process will be executed and a batch of prepaid cards will be created based on the input parameters. Detailed result page: 14

15 Card ID: the created card ID which is also the user ID based on the input parameters (batch prefix and start numbers based on card length) Password: created password based on the input parameters. Serial: the system card identificator. Card Batch: the card s batch Time Bank: the time bank value MB Bank: the MB bank value Card Price: the card price value Expiration Date: the expiration date if exist. Empty field means no expiration date Group Name: the associated card / user group Action: allows cancelling of prepaid cards. Generate Single Prepaid Card The Generate single prepaid cards page enables to generate a single card using the predefined card types. The following screenshot presents generation of a single card using a predefined card type: Please note: when there is no card type defined in the system, the list of card types will be empty and the Generate button will be disabled. Once pressing the 'Generate' button, the generation process will be executed and a single prepaid card will be created based on the selected card type. Detailed result page: 15

16 Manage Prepaid Cards The manage prepaid cards menu provides the user with full control over the batches and prepaid cards and supports status changes in various cases. Perform Operation: the field is a combo box which allows several options to be executed at the batch or card level. The following options are available: Change to Active allows activation of batches / cards. The option is available for batches / cards which were created as non-active. Change to Suspended allows suspension of batches / cards. Suspended cards can not be used. They can be changed to Active later. Cancel - allows cancellation of batches / cards. Canceled cards can no longer be reactivated. Batch: allows filtering based on a specific batch. The list presents the available batches in the system. 16

17 Card ID: allows operating on a single card. You need to populate the card ID. Business Entity: allows filtering based on a business entity. Card Type: the combo box presents the available card types and allows filtering based on it. For example, when multiple batches are using the same card type. Status: allows filtering based on the card status. Card price: allows filtering based on the card price. Depleted Only: allows filtering based on user metering banks depletion. Create date: allows filtering based on creation date. Start date: allows filtering based on start date. Expiration date: allows filtering based on expiration date. The following page presents an example for deactivating cards belonging to a specific batch: The list of cards that will be impacted by the operation is presented and you should press on the Confirm button to approve the operation to perform. Once pressing on the confirm button an approval massage will be displayed. 17

18 Prepaid Cards Reports The prepaid cards reports page allows generating detailed or summary reports for your prepaid cards. The following page allows you to define the criteria's for the reports: Report Type: allows selecting between a summary report and a detailed report. Summary report will present summaries at the batch level Detailed report will present details at the card level. Batch: allows filtering based on a specific batch. For example: when you want summary report for a single batch you need to choose the batch name from the combo box. Card ID: allows filtering based on a card ID. Status: allows filtering based on the card status. Business Entity: allows filtering based on a business entity. Card Type: allows filtering based on a card type. Serial: allows filtering based on the card internal identificator. Card Price: allows filtering based on card price. Depleted Only: allows filtering based on user metering depleted. Create Date: allows filtering based on card creation date. Start Date: allows filtering based on card start date. 18

19 Expiration date: allows filtering based on card expiration date. Export to File: when marking this flag you will be able to export the report details into a CSV file. Printable Report: when marking this flag you will be able to view the report in an output screen in printable format. Print option will be available for you. Summary report output page: Batch: the batch name. In case no batch name was used in the batch generation, the field will remain empty. The summary report displays a single line per batch. Business Entity: the business entity the cards were created under. When no business entity was selected in the cards generation, the field will remain empty. Total Cards: total cards in the batch (all statuses). Active cards: total of active cards in the batch. Non Active Cards: total of non active cards in the batch. Total Price: total price for all cards under the selected batch (cards in all statuses). Active Price: total price for all Active cards in the batch. 19

20 Detailed report output page: Batch: the batch the prepaid card belongs to. Card ID: the card ID. Serial: the internal card ID. Price: the price for the single prepaid card. Action: allows marking the prepaid card for cancel or sending s 20

21 Card Session Summary The card session summary page allows you to gather statistic and view detailed or summary reports for prepaid card sessions. The following page allows you to define and set the input parameters for your reports: Report Type: the report type field is a combo box presenting the available batches in the system. The field allows you to retrieve results for a specific batch. Report Subtype: the field specifies weather to present session lookup report for cards with sessions only, cards without sessions or both. Card ID: the field allows you to specify single card ID and hence present session details for a single user. Serial: allows filtering based on the card internal identificator. Date: the from and to fields allows you to filter your sessions based on a range of dates. Business Entity: allows you to filter sessions for a specific business entity. The combo box will present the available business entities in Aradial. Ascending: when marking this flag, the output results will be presented in ascending order. Printable Report: when marking this flag, the output results will be presented in printable format. Print button will be available on the screen Export to File: when marking this flag, the output results will be exported into a CSV file. The following screenshot presents an output for cards related to a specific batch which have sessions: 21

22 Card ID: the card ID the line is referring to. Clicking on the card ID hyperlink will connect you to the related user page. Total Sessions: the number of total sessions the card has. Group name: the group the card is associated with. Total Hours: the total hours used for the selected card in all sessions. Total in MB: the total in MB used for the selected card in all sessions. Total out MB: the total out MB used for the selected card in all sessions. From Date: the date of the first session for the selected card. To Date: the date of the last session for the selected card. Action: allows you to drill down for a detailed report for selected card. The following is a detailed report for selected card: 22

23 Chapter 5 Tiered Admin Access Proliferation of Administration Duties. In large setups, most administrative duties are divided between a number of persons the technical aspects of server configuration are handled by the technical manager or the system administrator, the support staff is in charge of solving user problems such as denied access due to wrong passwords, etc. Aradial, via its Tiered Admin Access feature, allows you to use sets of HTS files to which only designated personnel has access to, thus eliminating cases in which, for example, someone in the sales department might be tempted to play around with the server, and, accidentally, cause a server shutdown. The Tiered Admin Access of Aradial permits only the main Administrator to set access permissions to the users in the database, using the Admin Type field in the User page. Aradial comes with several levels of Tiered Admin Access, which may be customized: Full Rights This type of access is granted ONLY to the default user created when Aradial was first installed. This user can perform any action in Aradial, from configuring the server to adding users and view session reports. This right cannot be given to other users on your system. You may change this Administrator Interface by changing the level 1 HTS files (HTS levels are discussed below). Co-Admin This type of access may be granted by the Administrator to any of the users in the data base by setting their Admin Type value to Co-Admin. This user can perform, by default, all actions the Full Rights Administrator can perform, but grant an Admin Type level to another user. You may change this Administrator Interface by changing the level 3 HTS files (HTS levels are discussed below). Tech Support This user can perform all operations on Users, but doesn t have access to the prepaid cards and network configuration. You may change this Interface by changing the level 5 HTS files. Dealer Has access only to the cards/users assigned to his segment. You may change this Interface by changing the level 6 HTS files. 23

24 API This type of access may be granted by the Administrator to any of the users in the data base by setting their Admin Type value to API. This user is created to allow API interaction with Aradial, It doesn t have access to the UI. Session Reviewer This user is able to view online sessions and sessions statistics. You may change this Administrator Interface by changing the level 9 HTS files. User Reviewer This user is able to view users and sessions. You may change this Interface by changing the level 10 HTS files. Prepaid Card Generator This user has full access to the prepaid card management only. You may change this Interface by changing the level 11 HTS files. None This is the default access a user has set as his Admin Type value. The None level will inhibit users from accessing the Administrator Interface. There are no HTS files that may be altered for this Admin Type level, since no access is granted. You may easily create new levels of access by duplicating one level of HTS files, and altering the new set of HTS files to your requirements. Each HTS level is designated by a number in the Administrator HTS files directory ([Path to Aradial]\ \HTS\Admin). Although all level numbers (but level 1, which is reserved for the Full Rights Admin) have no real meaning (e.g. you can set the Co-Admin as level 67, instead of its default level 3), it might be wise to number the level in ascending order by level of permission (e.g. Co-Admin 3, System Administrator 4, User Manager 5, Technical Support 6, etc.). After creating a new HTS level, you should add the new level to the Rights.hts file in the Admin\1\ directory. This file is used as the source of data for the Admin Type selection box in the User edit page. The format of this file is as following: LevelNam en=levelnumbern$userdetails.admintype@ where: For example: LevelName is the name displayed in the Admin Type field in the User page. LevelNumber is the directory number under the HTS\Admin directory. Suppose you wish to add an Admin Type level named Online Sessions, which allows the level bearer to solely view the Online Session page in the Administrator Interface. For this example, we will number this level as 12: 1. Open a new directory named 12 under [ARADIAL path]\hts\admin\, so you have a new directory structure: [ARADIAL path]\hts\admin\12\. 24

25 2. Copy to this new directory the HTS files that should be available to users with this Admin Type. In this case, copy Sessions.hts, from Admin\1\ and rename it to index.hts (index.hts is the default page opened when opening the Administration Interface. 3. Edit HTS\Admin\1\Rights.hts using any text editor, such as notepad, and set the Sessions=12 4. Open the Administration Interface, and grant the relevant user Admin Type Online Sessions. Once this user logs on to the Administrator Interface, he will automatically access the Online Sessions page. Aradial UI Permissions Aradial supports configuring security permissions for administrative roles using a configuration file: AdminPermissions.conf, which consists of the following sections: 1. Role Name Definition. A role name definition is used to map between Aradial internal role number to its name: Role_[The internal number of the role]:[the name of the role] Role_5:CustomerService 2. Table Permission Definition. Defines what operations are allowed per entity. Operation may be Insert, Update or Delete: [Role].[Table].[Operation]:[Rights] Where Rights may be: * - All fields allowed, [Field Name] Comma separated list of allowed fields, Empty Nothing allowed. MainAdmin.Users.Insert:* CustomerService.Users.Update:UserId,Password UserRewiewer.Users.Delete: For those entities, which are not strictly defined, Default virtual table is used: MainAdmin.Default.Insert:* 3. Page Permission Definition. For each role it is possible to define allowed and disallowed page list. The page list is comma separated list of pages, where each element may be a wildcard: 25

26 CustomerService.AllowedPages:* CustomerService.DisallowedPages:DBSConfig,BalanceType*,BatchUsers,BillingCycleReport Where: - Allowed Pages is used to set the pages which are allowed to be used by the role. - Disallowed Pages - is used to set pages which are not allowed to be used by the role. 4. Special Options. There are some additional special options for operations that are not related to database updates: [Role].[Option]:[Value] - Configuration Update define whether to allow manipulation of configurations. - Daemon operations define whether to allow performing daemon operations such as starting and stopping the RADIUS server. MainAdmin.Daemon:1 MainAdmin.Configuration:1 Where a value of 1, Y or y means to allow, otherwise deny. 26

27 Chapter 6 Web Self Care Using Aradial as User s Web-Self-Care. Aradial provides a Wifi portal which is a web-based application that enables customers and users to browse and manage their own accounts. The portal can be customized to suit any provider's look and feel. With Aradial self care application, authorized users will have the following activities: View the user summary View user balances Update user details Change user password View and search the user sessions 27

28 Login to Aradial user self care: When a pre-defined user want to access to Aradial portal and view / manage his account he should access the Aradial portal URL ( The Aradial portal port is configurable and can be changed from the main admin Aradial screen Server Configuration Advanced Configuration HTTP Server WSC Interface Setting section, WSC Interface port parameter. Once Aradial authenticate and validate the user name and password, the Aradial User Self Care will present the User Summary Page: 28

29 User Summary The following sections will be presented in the User Summary tab: Personal Information: Aradial user self portal will present the user personal information with the registered data in 'read only' mode. Access Information: Aradial user self portal will present the user access information with the registered data in 'read only' mode. Additional access information: Aradial user self portal will present the user additional access information with the registered data in 'read only' mode. Dates: Aradial user self portal will present the dates information with the following details in 'read only' mode: User Creation date: The date the user was created in Aradial. User expiration date: the user expiration date. In case the user has no expiration date, the field will be empty. 29

30 User activation date: The user activation date as inserted in the user registration. In case no activation date was inserted, the user creation date will be presented. Last login on: the last login date for the specific user. This field is updated automatically by aradial and will present the most updated date. Metering information: User metering information will be presented. The data is automatically updated by Aradial based on the user' sessions. Data is presented in 'read only' mode. Update User The Update User page in the Aradial self care interface will allow the users to manage their own accounts and allow self update. Aradial will allow changing any of the user personal information but will not allow changing Metering info and / or any other system data information (e.g. user activation date, expiration date, tariff details, etc). The user will be able to change his personal information by changing the appropriate field and then pressing 'Update' button. The change will be reflected immediately. 30

31 Change Password Aradial self care portal is enabling the users to maintain and change their password information. Aradial will first authenticate and validate the old password and then allow changing to new password. The flow to change the user password is as follows: - The user login to the change password tab in the user self care - User type in the old password, new password and re-entering the new password - Aradial will authenticate the old password - If validation passes, the password will be replaced and appropriate massage will be displayed. - In case of validation error, password will not be changed and appropriate massage will be displayed. 31

32 View Sessions Aradial user self care interface is allowing the users to view their own sessions by login to the View sessions tab. Once login, the page will be displayed in search mode and will ask for data range criteria's for the search. Leaving the date fields empty means to range criteria's and Aradial self care will present all user sessions. Reset Will enable the user to reset the search criteria's and will remove the old values from the search fields. The search button will search the user sessions based on the input parameters, or all sessions if no parameters will be entered. The sessions screen will present the following information: Last update: the field will present the last login date and time when the user was connected. Login time: Login time in the session level. The field will present the session start time. Time online: the field will present the sessions duration. Service: This field will present the service the user is connected to and the session is related to. In MB: The field will present the used in MB (received MB) for the specific session. Out MB: The field will present the used out MB (sent MB) for the specific session. 32

33 Chapter 7 Wifi / Hotspot Portal Aradial Wifi Portal enables operators to create a wifi captive portal and to customize its look and feel to enable users login using their own login screen. Aradial provide all facilities to change the login page to include the provider logo, details and use Aradial self care functionalities. The following chapters describe the portal: - General explanation - Changing Aradial portal per location (provider) - Examples and instructions General explanation: Aradial portal receives parameters from the redirection URL of the router / access controller. This way once the user want to login he is redirected to the provider home page and needs to login with his personal details. The following example will demonstrate the flow for user connection (e.g. in hotel from the user room for example): - The user connects his/ her PC / laptop to the wifi lan and gets an IP address - The user opens his / her browser to connect the network - The user will automatically be redirected to a secured portal (SSL) - The user will be requested to login with his / her user name and password - The login details are sent by the router / access controller to Aradial for authentication - Aradial will reject or grant the user for login. 33

34 Please note: Aradial supports both http and https web access Changing Aradial portal per location (provider): As mentioned above, Aradial portal is receiving parameters from the access controller. The provider should configure the URL in the access controller For example: - Configure the URL: in the Linksys Chillispot access controller screen. - The following will automatically be added to the URL: uamip=12&uamport=123 - When it is redirected the URL would be: - The Portal javascript detects uamip=12&uamport=123 and knows it is chillispot. In the above example we can see that in the redirected URL the portal=msn link the user to the provider home page for user login. Aradial supports changing the look and feel web page using the portal parameter in the URL. The portal parameter can also link to a folder name which exist under: Aradial\Hts\Portal Example: The above link will redirect the user to the provider home page for user login, the portal parameter is linking to a directory called example1 and the web page look and feel can be customized in the Portal.hts file. Pictures and images can also be customized buy putting the *.png file in the specified directory. Instruction for changing Aradial portal per location: - Copy one of the examples directories under Aradial\Hts\Portal and rename it (e.g. New_Example) - Download editor like PSPad and edit the Portal.hts in order to change the content as requested - Change the picture (*.png file) to the requested logo - Configure the URL in the access controller to link to the specified directory Please note: More about Aradial Hts customization can be found in 'Hts customization' 34

35 Appendix F. Example1: The following example shows a portal that enables users login, self registration, self account management and more information regarding the service provider. The portal is built to suit specific provider logo and look & feel. Example2: Following is another sample portal for a different service provider. 35

36 36