Portal Server
This function helps you configure the system parameters required for normal operation of the Portal server. Proper parameter settings allow for easy Portal service management.
Precautions
- After configuring the Portal Server, you need to click User Access Policy > Service Parameters > Validate in the navigation tree to validate your configuration.
- If multiple operators simultaneously modify the Portal Server configuration, the latest configuration overwrites the former one.
Parameters
Basic Information
- Log Level: Limits the level of information to be logged by the system, currently including Fatal, Error, Warning, Info, and Debugging in descending order. If you select Fatal, the system logs only fatal errors. If you select Error, the system logs both fatal and general errors. If you select Warning, the system logs fatal, general and warning information. If you select Info, the system logs the fatal errors, general errors, warning information, and general information. If you select Debugging, the system logs all information, including all output packets and debugging information, which will greatly consume system resources. Therefore, it is not recommended to select Debugging in general use. The default log level is Info.
- Bind Port Groups to IP Group: Select Disable to allow an IP group to be used by only one port group. Select Enable to allow an IP group to be used by multiple port groups. If you select Enable for this parameter, the value for the Use Cache parameter is No by default and is not configurable.
Portal Server
- Request Timeout: Timeout of sending requests to the devices.
- Server Heartbeat Interval: Interval at which the Portal Server sends server heartbeat packets to portal access devices. For introduction of server heartbeat, refer to Portal Device.
- User Heartbeat Interval: Interval at which the Portal Server sends user heartbeat packets to portal access devices. For introduction of user heartbeat, refer to Portal Device.
- LB Device Address: IP address of the load balancing (LB) device.
- Disable Transparent Authentication for Offline Users: This feature prevents offline users from coming online again through transparent authentication. This feature applies only to users that initiate network disconnection.
- Transparent Authentication Check SSID: If enabled, when switching to an SSID for transparent authentication, users need to authenticate again. If disabled, when switching to an SSID for transparent authentication, users do not need to authenticate again.
Portal Web
- Request Timeout: Sets the timeout interval for the request packets sent from the Portal Web to the Portal Server, in secods. The value must be an integer in the range of 10 to 180.
- Packet Code: Specifies the code for packets exchanged between the Portal Web and the Portal Server. Typically, use default value GBK.
- Verify Endpoint Requests: Whether or not to verify headers of the HTTP request packets sent from endpoint users. If you select Yes, UAM can discard HTTP request packets sent by plug-ins to relieve the burden on Portal Web.
- Use Cache: Whether or not to use the cache when pushing pages to users. If you select Yes, UAM can reuse Web pages to relieve the burden on the Portal Web. However, the pushed pages might not be the latest. If you select No, UAM always pushes the latest pages to users.
- HTTP/HTTPS Heartbeat Display: Select a method to display the HTTP/HTTPS heartbeat page. Options are New Page and Original Page. If you select the New Page option, UAM creates a new Web page for the heartbeat page. If you select the Original Page option, UAM uses the original portal authentication page for the heartbeat page. The New Page option is also restricted by the browser type and settings. For example, if the browser prohibits popup windows, the option does not take effect and the heartbeat page must be displayed in the original portal authentication page. In the Chrome browser, the heartbeat page is always displayed in the original portal authentication page, because UAM cannot check whether or not the Chrome browser allows pop-up windows.
- Portal Page: Shows the URLs to the directories containing the portal authentication pages. Assume that two portal servers (A and B) are deployed, and their portal pages are at URL A and URL B respectively. If you specify the portal URL as URL A on an access device, users accessing the network through the access device will be redirected to portal server A for authentication.
Advanced Information
- Service Type ID: The device determines the authentication mode according to the selected service type. You can make appropriate setting here according to the configuration of the INC services and devices.
- Service Type: The service type ID is used by the device. Users could not understand what it means straightforwardly. The service type displayed in the Portal login homepage gives the user an explanation of the service type. This field can neither be null nor be identical with any existing service type.You can configure 64 service types at most.
Related Topics