Configuration Captive Portal

Setup Captive Portal on-premises

  1. Access to your Captive Portal server
  2. Locate your .env config file, by default the path should be dnat-server/.env
  3. Input the License key that link to your MetaDefender IT Access Profile
  4. Input SNI Server address and DNAT Server address

Configurate Captive Portal Profile

Aruba

To configure Access Rules for Network Vendors that support DNAT (ex: Aruba), perform the below steps:

  1. On Access Profiles tab, create a Access Profile for Captive Portal
  2. On Aruba drop-down, declare a values (ex: ORG_B_2084RDR) for Aruba-User-Role attributes
  1. On Rules tab, add a new Rule and select to assign to the above Captive Portal profile
  1. On the Network Vendor (ex: Aruba) console, create an ACL (Network Access Control List) to forward traffic to your DNAT server

How to verify

  1. Using a test device & Connect to the Network
  2. If the agent is not installed on that machine, it will match with the Captive Portal rule and redirect user to the Captive Portal page to download the agent
  1. From RADIUS Events log, we can observe that the device is matching Captive Portal rule
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
Configure EAP-TLS
On This Page
Configuration Captive PortalSetup Captive Portal on-premisesConfigurate Captive Portal ProfileArubaHow to verify