Configuring direct portal authentication

Network requirements

As shown in Figure 54, the host is directly connected to the switch (the access device). The host is assigned a public IP address either manually or through DHCP. A portal server acts as both a portal authentication server and a portal Web server. A RADIUS server acts as the authentication/accounting server.

Configure direct portal authentication, so the host can access only the portal server before passing the authentication and access other network resources after passing the authentication.

Figure 53: Network diagram

Configuration prerequisites

Configuring the portal authentication server on IMC PLAT 5.0

In this example, the portal server runs on IMC PLAT 5.0(E0101) and IMC UAM 5.0(E0101).

  1. Configure the portal authentication server:

    1. Log in to IMC and click the Service tab.

    2. Select User Access Manager > Portal Service Management > Server from the navigation tree to open the portal server configuration page, as shown in Figure 55.

    3. Configure the portal server parameters as needed.

      This example uses the default settings.

    4. Click OK.

    Figure 54: Portal server configuration

  1. Configure the IP address group:

    1. Select User Access Manager > Portal Service Management > IP Group from the navigation tree to open the portal IP address group configuration page.

    2. Click Add to open the page as shown in Figure 56.

    3. Enter the IP group name.

    4. Enter the start IP address and end IP address of the IP group.

      Make sure the host IP address is in the IP group.

    5. Select a service group.

      This example uses the default group Ungrouped.

    6. Select the action Normal.

    7. Click OK.

    Figure 55: Adding an IP address group

  1. Add a portal device:

    1. Select User Access Manager > Portal Service Management > Device from the navigation tree to open the portal device configuration page.

    2. Click Add to open the page as shown in Figure 57.

    3. Enter the device name NAS.

    4. Enter the IP address of the switch's interface connected to the host.

    5. Enter the key, which must be the same as that configured on the switch.

    6. Set whether to enable IP address reallocation.

      This example uses direct portal authentication, and therefore select No from the Reallocate IP list.

    7. Select whether to support server heartbeat and user heartbeat functions.

      In this example, select No for both Support Server Heartbeat and Support User Heartbeat.

    8. Click OK.

    Figure 56: Adding a portal device

  1. Associate the portal device with the IP address group:

    1. As shown in Figure 58, click the icon in the Port Group Information Management column of device NAS to open the port group configuration page.

    2. Click Add to open the page as shown in Figure 59.

    3. Enter the port group name.

    4. Select the configured IP address group.

      The IP address used by the user to access the network must be within this IP address group.

    5. Use the default settings for other parameters.

    6. Click OK.

    Figure 57: Device list

Figure 58: Adding a port group

  1. Select User Access Manager > Service Parameters > Validate System Configuration from the navigation tree to validate the configurations.

Configuring the switch

  1. Configure a RADIUS scheme:

    # Create a RADIUS scheme named rs1 and enter its view.

    <Switch> system-view
    [Switch] radius scheme rs1
    

    # Specify the primary authentication server and primary accounting server, and configure the keys for communication with the servers.

    [Switch-radius-rs1] primary authentication 192.168.0.112
    [Switch-radius-rs1] primary accounting 192.168.0.112
    [Switch-radius-rs1] key authentication simple radius
    [Switch-radius-rs1] key accounting simple radius
    

    # Exclude the ISP domain name from the username sent to the RADIUS server.

    [Switch-radius-rs1] user-name-format without-domain
    [Switch-radius-rs1] quit
    

    # Enable RADIUS session control.

    [Switch] radius session-control enable
    
  2. Configure an authentication domain:

    # Create an ISP domain named dm1 and enter its view.

    [Switch] domain dm1
    

    # Configure AAA methods for the ISP domain.

    [Switch-isp-dm1] authentication portal radius-scheme rs1
    [Switch-isp-dm1] authorization portal radius-scheme rs1
    [Switch-isp-dm1] accounting portal radius-scheme rs1
    [Switch-isp-dm1] quit
    

    # Configure domain dm1 as the default ISP domain. If a user enters the username without the ISP domain name at login, the authentication and accounting methods of the default domain are used for the user.

    [Switch] domain default enable dm1
    
  3. Configure portal authentication:

    # Configure a portal authentication server.

    [Switch] portal server newpt
    [Switch-portal-server-newpt] ip 192.168.0.111 key simple portal
    [Switch-portal-server-newpt] port 50100
    [Switch-portal-server-newpt] quit
    

    # Configure a portal Web server.

    [Switch] portal web-server newpt
    [Switch-portal-websvr-newpt] url http://192.168.0.111:8080/portal
    [Switch-portal-websvr-newpt] quit
    

    # Enable direct portal authentication on VLAN-interface 100.

    [Switch] interface vlan-interface 100
    [Switch–Vlan-interface100] portal enable method direct
    

    # Reference the portal Web server newpt on VLAN-interface 100.

    [Switch–Vlan-interface100] portal apply web-server newpt
    

    # Configure the BAS-IP as 2.2.2.1 for portal packets sent from VLAN-interface 100 to the portal authentication server.

    [Switch–Vlan-interface100] portal bas-ip 2.2.2.1
    [Switch–Vlan-interface100] quit
    

Verifying the configuration

# Verify that the portal configuration has taken effect.

[Switch] display portal interface vlan-interface 100
 Portal information of Vlan-interface100
     NAS-ID profile: Not configured
     VSRP instance : Not configured
     VSRP state    : N/A
     Authorization : Strict checking 
     ACL           : Disabled
     User profile  : Disabled
 IPv4:
     Portal status: Enabled
     Portal authentication method: Direct
     Portal web server: newpt
     Authentication domain: Not configured
     Pre-auth domain: Not configured
     User-dhcp-only: Disabled
     Pre-auth IP pool: Not configured
     Max Portal users: Not configured
     Bas-ip: 2.2.2.1
     User Detection:  Not configured
     Action for server detection:
         Server type    Server name                        Action 
         --             --                                 -- 
     Layer3 source network:
         IP address               Mask

     Destination authenticate subnet:
         IP address               Mask
IPv6:
     Portal status: Disabled
     Portal authentication method: Disabled
     Portal web server: Not configured
     Authentication domain: Not configured
     Pre-auth domain: Not configured
     User-dhcp-only: Disabled
     Pre-auth IP pool: Not configured
     Max Portal users: Not configured
     Bas-ipv6: Not configured
     User detection: Not configured
     Action for server detection:
         Server type    Server name                        Action
         --             --                                 --
     Layer3 source network:
         IP address                                        Prefix length

     Destination authenticate subnet: 
         IP address                                        Prefix length

A user can perform portal authentication by using the HPE iNode client or through a Web browser. Before passing the authentication, the user can access only the authentication page http://192.168.0.111:8080/portal. All Web requests from the user will be redirected to the authentication page. After passing the authentication, the user can access other network resources.

# After the user passes authentication, use the following command to display information about the portal user.

[Switch] display portal user interface vlan-interface 100
 Total portal users: 1
  Username: abc
  Portal server: newpt
  State: Online
  VPN instance: N/A
  MAC                IP                 VLAN   Interface
  0015-e9a6-7cfe     2.2.2.2            100    Vlan-interface100
  Authorization information:
    DHCP IP pool: N/A
    ACL: N/A
    CAR: N/A