DOCSLIB.ORG

Configuring Fortigate with Forticonnect As External Captive Portal

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Configuring Fortigate with Forticonnect As External Captive Portal Configuring FortiGate with FortiConnect as External Captive Portal 1 FortiConnect can be configured as the external captive portal for authenticated internet access in a FortiGate deployment. This document focuses on the configurations required on the FortiGate controller and FortiConnect to form a seamless conjunction. This document describes configurations ONLY for wireless guest access. For wired guest access, you need to create a VLAN interface on your FortiGate and configure it to use a Captive Portal as per the procedure described in this document and have that wired VLAN available as an untagged/access VLAN on the guest device switch port. 2 Before You Begin Ensure the following pre-requisites are fulfilled prior to configuring your setup. Connect to the FortiGate and verify that the access points are discovered by the Controller and are operational in the Online state. Navigate to WiFi & Switch Controller > Managed FortiAPs. The FortiAP profile is created and applied to the access point on the FortiGate. The FortiConnect setup is installed and complete. Valid PKI certificates are installed to prevent certificate errors on client devices. Create an address object for FortiConnect. Create an address object for your DNS server hosting the FQDN for FortiConnect. 3 4 Configuring FortiGate Complete these configurations on the FortiGate user interface. Configuring the RADIUS Server Navigate to User & Device > RADIUS Servers; click Create New and populate the configuration page as per your network requirements. The following configurations are mandatory: Name – Specify the name of the FortiConnect. NAS IP – Specify the FortiGate interface IP address used to communicate with FortiConnect. If RADIUS accounting is required, use the following commands: config user radius edit FortiConnect set server 10.1.10.5 <FortiConnect IP address> set secret xxxxxxxxxx set nas-ip X.X.X.X <FortiGate Interface IP> (used to communicate with FortiConnect) set acct-all-servers enable (enables RADIUS accounting) set acct-interim-interval (configures time between each accounting interim update message) Primary Server – Specify the name or IP address of FortiConnect. Secret – Specify the shared secret to communicate with the server. 5 6 Configuring the Remote Guest User Group Create a new remote user group and assign FortiConnect as the authentication platform. Navigate to User & Device > User Groups; click Create New and populate the configuration page as per your network requirements. The following configurations are mandatory: Name- A unique name for the user group. Type – Select Firewall for authentication. Remote Groups - Click +Add and select RADIUS server created in Configuring the RADIUS Server. 7 Configuring the Wireless Interface Configure SSID and Captive Portal authentication. Navigate to WiFi & Switch Controller > SSID; click Create New and populate the configuration page as per your network requirements. The following configurations are mandatory: Interface Name – Specify the name of the SSID interface. Type – Select WiFi SSID. Traffic Mode – Select Tunnel. IP/Network Mask – Specify the IP address and netmask for the SSID. Enable DHCP Server and retain the default address range. Configure the following WiFi Settings for the captive portal. SSID - Specify the SSID. Security Mode - Select the Captive Portal security mode for the wireless interface. 8 Portal Type - Select Authentication as the captive portal type. Authentication Portal – Complete the FortiConnect setup in Configuring FortiConnect before proceeding further. Specify the FQDN or IP address of the FortiConnect. Enter the steering/redirection URL obtained from FortiConnect in the following formats: connect.fortixpert.com/portal/<DEVICEIP = RADIUS NAS-IP> Example: connect.fortixpert.com/portal/<10.1.10.1> OR <FortiConnect_IP>/portal/<FortiGate_NAS_IP> Example: <10.1.10.5>/portal/<10.1.10.1> The external portal URL requires you to remove the https:// prefix. User Groups - Select permitted user groups for captive portal authentication; select the user group created in Configuring the Remote Guest User Group. Exempt Destinations/Devices – Specify FortiConnect address object and the DNS service. 9 Configuring Outgoing Policies Create an outbound IPV4 policy for Guest Portal access. Create another outbound access to the internet once authenticated via the Captive Portal Guest Portal Policy Navigate to Policies & Object > IPv4 Policy; click Create New and populate the configuration page as per your network requirements. The following configurations are mandatory: Name - Specify the name of the policy. Incoming Interface - Select the SSID created in Configuring the Wireless Interface. Outgoing interface - Select the interface facing FortiConnect. Source - Select all as the source of the initiating traffic. Destination - Select the DNS-Server and FortiConnect address objects. Service - Select DNS, HTTP and HTTPS. Disable NAT. 10 Login into the FortiGate CLI console and run the following commands to allow access to the external FortiConnect Captive Portal page. config firewall policy edit <New Guest Portal Policy ID> set captive-portal-exempt enable end Internet Access Policy Navigate to Policies & Object > IPv4 Policy; click Create New and populate the configuration page as per your network requirements. The following configurations are mandatory: Name - Specify the name of the policy. Incoming Interface - Select the SSID created in Configuring the Wireless Interface. Outgoing interface - Select the interface facing the internet. Source - Select all and the user group created in Configuring the Remote Guest User Group as the source of the initiating traffic. Destination - Select All as the destination parameter. 11 Configuring FortiConnect Login into the FortiConnect portal using the FortiConnect IP address or FQDN - https://[FortiConnect FQDN]/admin OR https://[FortiConnect IP address]/admin Configuring FortiGate as the RADIUS client Navigate to Devices > RADIUS Clients; click Add RADIUS Client and populate the configuration page as per your network requirements. The following configurations are mandatory: Name – Specify the name of the FortiGate appliance. Device IP Address – Specify the FortiGate IP address (Guest address that communicates with FortiGate). Secret – Specify the same shared secret configured for the RADIUS server on FortiGate. Type – Select FortiGate. Change of Authorization – Select Use CoA and Proxy CoA. 12 Obtaining Captive Portal Steering Path Navigate to Guest Portals > Portals and modify the Default login portal settings to as per your requirements. On the Portal Policy > Redirection page, click Next to obtain the steering/redirection URL. The redirection URL is the external address for the captive portal and is available in the format - https://[FORTICONNECT FQDN]/portal/login/[NAS-IP address]. Examples https://connect.fortixpert.com/portal/login/10.1.10.1 OR https://connect.fortixpert.com/portal/10.1.10.1 An FQDN and a valid PKI web server certificate must be implemented on FortiConnect to avoid certificate errors when user devices connect to the Captive Portal. The redirection path includes the specific portal name. If you have multiple portals configured and want to use rules to direct users to different portals. You need to remove the specific portal name from the redirection URL, that is, https://connect.fortixpert.com/portal/10.0.1.20. 13 Configuring Authentication Server FortiConnect can be used as a user database. Users can be provisioned through the Sponsor Portal (https://connect.fortixpert.com/sponsor) or self-provisioned by a guest only if the Guest Portal is configured to support this functionality. Alternatively, a third party user database can be selected. To use a third party user database, navigate to Network Access Policy > Authentication Policy and click on Add Server, select an authentication server type and follow the wizard through to completion. 14 Validating User Access To test and validate the success of the setup connect to the guest WiFi network from a wireless enabled device; the guest portal should load within seconds. 1. [If using guest self-sign-on] Update the Self Service section and click Generate Account. Note down your login details. 2. [If using guest self-sign-on] Click the login button to go back to the portal Login screen, enter your login details and you should now be on the guest Wi-Fi network and have access to the internet. In the FortiGate GUI, navigate to Log & Report > Monitor > Firewall User Monitor and verify that the guest has logged in. You can also monitor the user at Log & Report > Monitor > WiFi Client Monitor. 15 .
Load more

Recommended publications
  • Technical Impacts of DNS Privacy and Security on Network Service Scenarios
    - Technical Impacts of DNS Privacy and Security on Network Service Scenarios ATIS-I-0000079 | April 2020 Abstract The domain name system (DNS) is a key network function used to resolve domain names (e.g., atis.org) into routable addresses and other data. Most DNS signalling today is sent using protocols that do not support security provisions (e.g., cryptographic confidentiality protection and integrity protection). This may create privacy and security risks for users due to on-path nodes being able to read or modify DNS signalling. In response to these concerns, particularly for DNS privacy, new protocols have been specified that implement cryptographic DNS security. Support for these protocols is being rapidly introduced in client software (particularly web browsers) and in some DNS servers. The implementation of DNS security protocols can have a range of positive benefits, but it can also conflict with important network services that are currently widely implemented based on DNS. These services include techniques to mitigate malware and to fulfill legal obligations placed on network operators. This report describes the technical impacts of DNS security protocols in a range of network scenarios. This analysis is used to derive recommendations for deploying DNS security protocols and for further industry collaboration. The aim of these recommendations is to maximize the benefits of DNS security support while reducing problem areas. Foreword As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industry’s business priorities. ATIS’ 150 member companies are currently working to address network reliability, 5G, robocall mitigation, smart cities, artificial intelligence-enabled networks, distributed ledger/blockchain technology, cybersecurity, IoT, emergency services, quality of service, billing support, operations and much more.
    [Show full text]
  • Captive Portal Detection Error May Be Triggered If There Is HTTP 302 Response Code Received PRS-325375 While Connecting to IVE
    Pulse Connect Secure Release Notes 8.1 R4 Build 37085: July 2015 Revision 01 Contents Introduction......................................................................................................................... 1 Interoperability and Supported Platforms ............................................................................ 2 Noteworthy changes in 8.1r4 Release ................................................................................ 2 Problems Resolved in 8.1R4 Release ................................................................................ 2 Known Issues in 8.1R3.2 release ....................................................................................... 4 Problems Resolved in 8.1R3.1 Release ............................................................................. 4 Pulse Connect Secure New Features in 8.1R3 ................................................................... 5 Noteworthy changes in this Release................................................................................... 6 Problems Resolved in 8.1R3 Release ................................................................................ 6 Known Issues in this release .............................................................................................. 7 Pulse Connect Secure Access New Features in 8.1R2 Release ........................................ 8 Disable TLS 1.0 ....................................................................................................... 8 New Functionality to create role mapping rules
    [Show full text]
  • Filtering and Identifying Web Activity by User Name
    Wavecrest®TechBrief Filtering and Identifying Web Activity by User Name www.wavecrest.net When a company implements a Web filtering and monitoring solution, it typically wants to filter and monitor the Web traffic flowing through its network by user name versus IP address for various reasons. Some of these reasons include curtailing casual surfing, protecting against security threats, and conserving bandwidth. Furthermore, a company’s Acceptable Use Policy (AUP) is usually based on user names and/or groups of user names. Therefore, the application that enforces and monitors the company’s AUP needs to identify Web activity by user name. IP addresses can be dynamic, and sometimes more than one employee can log on to a computer, and hence, more than one user name will be using the same IP address. Many an IT administrator is tasked with ensuring that the company’s employees are going through the proxy that is in place, so that Web activity can be monitored by user name. To get user names and authenticate users, IT administrators can choose any of the proxy configuration options and authentication methods described below. Depending on the company’s preference, one proxy configuration option may be more favorable than the other. Here, we will discuss applying browser settings manually, pushing out group policies using Active Directory (AD), using a captive portal, and installing client software. We will also touch on the different ways that you can authenticate your Internet users using our CyBlock products. Applying Browser Settings Manually Applying browser settings involves identifying a proxy server which is required if you need user names.
    [Show full text]
  • 9 Caching Proxy Server
    webXaccelerator: Owner's Guide by Luis Soltero, Ph.D., MCS Revision 1.06 February 10, 2010 (v1.2.3.10-RELEASE) Copyright © 2010 Global Marine Networks, LLC Table of Contents 1 Quick Start..............................................................................................................................................5 2 Introduction.............................................................................................................................................8 3 Initial Installation and Configuration......................................................................................................9 3.1 Connections.....................................................................................................................................9 3.2 Power-up..........................................................................................................................................9 3.3 Power-down...................................................................................................................................10 3.4 Web Administrator........................................................................................................................10 3.5 LAN Setup.....................................................................................................................................10 3.6 WAN Setup....................................................................................................................................11 3.7 WAN2 (Backup WAN) Setup........................................................................................................13
    [Show full text]
  • Tunneled Internet Gateway Wi-Fi Access for Mobile Devices in High-Security Environments Table of Contents
    WHITE PAPER TUNNELED INTERNET GATEWAY Wi-FI ACCESS FOR MOBILE DEVICES IN High-SECURitY ENVIRONMENTS TABLE OF CONTENTS THE ChALLENGE: Wi-FI ACCESS FOR MOBILE DEVICES IN high-SECURitY ENVIRONMENTS 3 ARUBA TUNNELED INTERNET GATEWAY SOLUtiON 3 HOW thE TUNNELED INTERNET GATEWAY WORKS 3 APPENDIX 5 TOPOLOGY DIAGRAMS 8 ABOUT ARUBA NETWORKS, INC. 9 WHITE PAPER TUNNELED INTERNET GATEWAY THE CHALLENGE: WI-FI ACCESS FOR MOBILE HOW THE TUNNELED INTERNET GATEWAY WORKS DEVICES IN HIGH-SECURITY ENVIRONMENTS Summary Since the debut of the iPhone in 2007, the private sector The Tunneled Internet Gateway is enabled through software has seen a proliferation of personal mobile devices used in configuration to any new or existing controller-based Aruba the workplace. Government customers, while slower to WLAN. Mobile users connect their devices to the Internet adopt commercially available mobile devices in the gateway SSID, creating an encrypted session with an Aruba workplace, recognize the cost and productivity advantages Mobility Controller deployed in the restricted network. and are looking for ways to increase their usage and speed- up adoption. The controller maintains logical separation between Internet sessions and restricted sessions using a Common Criteria Many civilian and military organizations have already begun EAL4+ validated firewall, then routes Internet traffic through large-scale acquisitions of commercial off-the-shelf (COTS) an additional encrypted data tunnel to a router attached to a mobile devices for distribution to relevant personnel. The commercial Internet service provider. The result is a secure, February 2013 purchase by the U.S. Department of Defense simple and low-cost network overlay with strong separation of 630,000 Apple iOS-based mobile devices is just one between restricted and Internet data.
    [Show full text]
  • Anyconnect Captive Portal Detection and Remediation
    Contents Introduction Prerequisites Requirements Components Used Background Information Captive Portal Remediation Requirements Captive Portal Hotspot Detection Captive Portal Hotspot Remediation False Captive Portal Detection AnyConnect Behavior Captive Portal Incorrectly Detected with IKEV2 Workarounds Disable the Captive Portal Feature Introduction This document describes the Cisco AnyConnect Mobility Client captive portal detection feature and the requirements for it to function correctly. Many wireless hotspots at hotels, restaurants, airports, and other public places use captive portals in order to block user access to the Internet. They redirect HTTP requests to their own websites that require users to enter their credentials or acknowledge terms and conditions of the hotspot host. Prerequisites Requirements Cisco recommends that you have knowledge of the Cisco AnyConnect Secure Mobility Client. Components Used The information in this document is based on these software versions: ● AnyConnect Version 3.1.04072 ● Cisco Adaptive Security Appliance (ASA) Version 9.1.2 The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Background Information Many facilities that offer Wi-Fi and wired access, such as airports, coffee shops, and hotels, require users to pay before they obtain access, agree to abide by an acceptable
    [Show full text]
  • Browser History Stealing with Captive Wi-Fi Portals
    Browser History Stealing with Captive Wi-Fi Portals Adrian Dabrowski, Georg Merzdovnik, Nikolaus Kommenda, Edgar Weippl [email protected] Twitter: @atrox_at 2016-05-26 Public Wi-Fi Hotspots ● Like a well in a village Internet ● We gather there, pull up a bucket or two of “Internet” ● Look at the sign from the sponsor ● … and move on. What is a “Captive Portal”? Why Captive Portal ● Omnipresent in Wi-Fi Hotspots ● Used by you probably right now (in this very hotel) ● Has an elevated position on the network ● Man-in-the-Middle by design ● Sponsors of a Wi-Fi want us to see their messages (and accept the disclaimer) ● There is no standard for that ● Let's inject it into your traffic… Browser History Stealing, again? ● Baron, 2002 ● :visited link color TODO: ● Ruderman, 2000 Groundhog ● :visited can load images ● Jang, 2010 ● Sites are actively trying to steal history History, so what? ● Culture & Language ● Amazon.fr, Amazon.jp ● Sexual orientation ● grindr.com, transblog.de ● Other websites that give ● Partnership status interesting insights ● Okcupid.com, parship.com ● Medical conditions ● Employer ● Political campaigns ● intranet.ibm.com ● Religious communities Source: MindSource April 1996 BOF; Client State Tracking with Netscape Cookies; M. Strata Rose; [email protected] Source: MindSource April 1996 BOF; Client State Tracking with Netscape Cookies; M. Strata Rose; [email protected] Cookies (or not enough state for HTTP) ● Two kinds ● Session cookies: usually forgotten when browser closed ● Persistent cookies: stored on disk with expiry date ● Only depend on the FQDN and Protocol ● XSS ● XSRF ● HTTP set cookie also used for HTTPS – Insecure set cookies mixed into the cookies over HTTPS http://cnn.com (+cookies) 302 redirect login.hotspotsys.com/login login.hotspotsys.com/login <html>….
    [Show full text]
  • Captive Portal
    User module Captive Portal APPLICATION NOTE USED SYMBOLS Used Symbols Danger – important notice, which may have an influence on the user’s safety or the function of the device. Attention – notice on possible problems, which can arise in specific cases. Information, notice – information, which contains useful advice or special interest. GPL License Source codes under GPL license are available free of charge by sending an email to: [email protected]. Conel s.r.o., Sokolska 71, 562 04 Usti nad Orlici, Czech Republic Manual issued in CZ, October 6, 2014 i CONTENTS Contents 1 Description of user module 1 2 Configuration 2 2.1 Global ......................................... 2 2.2 Welcome page .................................... 4 2.3 QoS .......................................... 4 3 How to create own welcome page 6 3.1 Simple page ...................................... 6 3.2 Login page ...................................... 6 3.3 Ban page ....................................... 7 3.4 Customized original URL .............................. 7 3.5 Example ........................................ 7 4 Status Overview 9 5 Recommended literature 10 ii LIST OF FIGURES List of Figures 1 Web Interface ..................................... 1 2 Global configuration form .............................. 3 3 Welcome page configuration form ......................... 4 4 QoS configuration form ............................... 5 iii LIST OF TABLES List of Tables 1 Available services .................................. 9 2 Connected customers ................................ 9 iv 1. DESCRIPTION OF USER MODULE 1. Description of user module User module Captive Portal is not contained in the standard router firmware. Uploading of this user module is described in the Configuration manual (see [1, 2]). Please note that this module is compatible only with firmware 4.0.0 or later in v2 routers! The user module is v3 routers platform compatible.
    [Show full text]
  • Captive Portal Authentication Via Facebook
    Grandstream Networks, Inc. Captive Portal Authentication via Facebook Table of Content SUPPORTED DEVICES ................................................................................................ 4 INTRODUCTION ............................................................................................................ 5 CAPTIVE PORTAL SETTINGS ..................................................................................... 6 Policy Configuration Page ................................................................................................................7 Landing Page Redirection ....................................................................................................... 10 Pre-Authentication Rules ........................................................................................................ 10 Post-Authentication Rules ....................................................................................................... 10 Guest Page ................................................................................................................................... 11 CONFIGURATION STEPS........................................................................................... 12 Create Facebook App .................................................................................................................... 12 Configure Captive Portal Policy with Facebook Authentication ....................................................... 17 Using GWN Master GUI (Standalone mode) ..........................................................................
    [Show full text]
  • Browser History Stealing with Captive Wi-Fi Portals
    Browser History Stealing with Captive Wi-Fi Portals Adrian Dabrowski∗, Georg Merzdovnik∗, Nikolaus Kommenday and Edgar Weippl∗ ∗SBA Research, Vienna, Austria Email: [email protected] yTechnische Universitat¨ Wien, Vienna, Austria Email: [email protected] Abstract—In this paper we show that HSTS headers and in public Wi Fi hotspot systems such as cafes,´ restaurants, long-term cookies (like those used for user tracking) are so airports, and hotels. The user is informed about the spon- prevailing that they allow a malicious Wi-Fi operator to gain significant knowledge about the past browsing history of users. sor of the access, possible restrictions as well as potential We demonstrate how to combine both into a history stealing payment methods and has to accept terms and conditions. attack by including specially crafted references into a captive After completion, the user is given access to the Internet. portal or by injecting them into legitimate HTTP traffic. Especially in transit areas the majority of users use hand-held Captive portals are used on many Wi-Fi Internet hotspots to devices such as tablets and smart phones. Additionally, these display the user a message, like a login page or an acceptable use policy before they are connected to the Internet. They are devices automatically connect to known Wi Fi access points. typically found in public places such as airports, train stations, or We specifically elaborate on these cases and their implications. restaurants. Such systems have been known to be troublesome for Public hotspots have been known to be troublesome in many many reasons.
    [Show full text]
  • Web Request Routing and Redirection What’S the Best Option for Your Web Security Deployment?
    Technical Brief Web Request Routing and Redirection What’s the best option for your web security deployment? Web Request Routing and Choosing the right method for redirecting traffic to your secure web gateway is Redirection absolutely essential to maximize protection for users who are accessing the Internet Key routing methods • Browser plug-ins. either on site within the corporate firewall or on the go. How you do it depends • Explicit proxy. on the available configuration options for your web security solution, your unique • Client proxy. IT infrastructure, and your chosen method of deployment. Never before have • Proxy auto-configuration (PAC). organizations of all sizes and infrastructure configurations had so many deployment • Generic routing encapsulation (GRE). choices for multi-layered web security. Flexible implementation options include on-premises appliances and blade servers, Software-as-a-Service (SaaS), or hybrid Key supporting technologies combinations. Secure web gateways in all of these form factors aim to protect users, • Web proxy auto-discovery (WPAD). devices, and networks against increasingly malicious and complex web threats through • VPNs, firewalls, routers, and inbound and outbound web filtering, advanced antivirus and anti-malware, and perimeter devices. policy enforcement. • Mobile device management. • IP anycast proxy URLs. Location. Location. Location. Where are your users and devices when they access the Internet? This is a key consideration in determining the best methods for redirecting web traffic to a secure web gateway solution. Whichever methods you choose, you must take into account user experience in terms of latency (performance degradation), location of the user, the device in use; ease of deployment and management; and above all, level of protection.
    [Show full text]
  • IB7200 - Connectivity in ICT4D
    IB7200 - connectivity in ICT4D Lecture 3 DNS - domain name system Mapping name and ipnumbers. Forward: name to number nic.lth.se. IN A 130.235.20.3 Reverse: number to name 3.20.235.130.in-addr.arpa. IN PTR nic.lth.se. DNS lookup Routing protocols Packets need to find way through net Static routing: Each way is added manually. Normally don’t use, gets messy very soon… Instead use dynamic routing Routing info protocol (RIP) Simple, early protocol. Distance vector. (low overhead) Rip v2 better. Never use rip v1. Avoid rip v2 Dynamic routing - OSPF Open Shortest Path First (OSPF) Used inside organisation. Very stable and compatible between vendors. Uses link state algoritm: All routers know the whole topology. Requires more computational power (no problem today) Border Gateway Protocol (BGP) Used between organizations (borders) Between autonomous systems (AS) Each AS has a number 0-65000 Can decide “policy routing” like not allowing traffic from some AS. My ORG Other ORG BGP OSFP AS y AS x Summary Use OSPF internally + BGP externally External AS2 External AS1 BGP BGP OSFP Multicast Send to many on a network. Internet Group Management Protocol (IGMP). Adresses 224.0.0.0 to 239.255.255.255 PIM - protocol independent multicast Within an organisation Multicast Source Discovery Protocol (MSDP) Between organisations IPv6 128 bit addreses. Written in hex. 2001:6b0:1:1d20:214:c2ff:fe3a:5eec/64 64 bit net + 4 bit host Host is normally 12 bit fill + 48 bit mac-addr Each “nibble” (character) is 4 bit KTH has 2001:6b0:1::/48 2001:06b0:0001 ie we have 2^18 networks each with 2^64 hosts… Wireless Local area - WiFi - WLAN 802.11* Metro - WIMAX 802.16 Wide area - GPRS: GSM, UMTS-3G VSAT - slow expensive but necesary in some places.
    [Show full text]