HP 5500 HI Series Configuration Manual page 138

3. The portal server assembles the username and password into an authentication request message
and sends it to the access device. Meanwhile, the portal server starts a timer to wait for an
authentication acknowledgment message.
4. The access device and the RADIUS server exchange RADIUS packets to authenticate the user.
5. The access device sends an authentication reply to the portal server.
6. The portal server sends an authentication success message to the authentication client to notify it of
logon success.
7. The portal server sends an authentication reply acknowledgment message to the access device.
With extended portal functions, the process includes additional steps:
8. The security policy server exchanges security check information with the authentication client to
check whether the authentication client meets the security requirements.
9. Based on the security check result, the security policy server authorizes the user to access certain
resources, and sends the authorization information to the access device. The access device then
controls access of the user based on the authorization information.
Re-DHCP authentication process (with CHAP/PAP authentication)
Figure 41 Re-DHCP authentication process
The re-DHCP authentication takes the following procedure:
The first steps are the same as those in the direct authentication/cross-subnet authentication process.
1. After receiving the authentication success message, the authentication client obtains a new public
IP address through DHCP and notifies the portal server that it has obtained a public IP address.
2. The portal server notifies the access device that the authentication client has obtained a new public
IP address.
3. Detecting the change of the IP address by examining ARP packets received, the access device
notifies the portal server of the change.
125