Business Community > Controllers > Access Control Configuration for External Captive Portal
< Controllers

Access Control Configuration for External Captive Portal

Access Control Configuration for External Captive Portal

Access Control Configuration for External Captive Portal
Access Control Configuration for External Captive Portal
Thursday - last edited Friday
Tags: #Controller #Portal
Model: Omada Software Controller (Linux)   EAP225  
Hardware Version:
Firmware Version:

I have an SDN controller v5.15.8 that I deployed under domain name 1, and I enabled the external captive portal hosted at domain name 2.

My question is: in the Access Control section, do I need to add both domains along with the IP address of my Omada domain? Or do I only need to add the captive portal domain and the IP address of my Omada server.
 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Access Control Configuration for External Captive Portal-Solution
Friday - last edited Friday

Hi  @Rayen_CR 

 

Thanks for posting here.

 

Must Allow:

  • The IP address (or domain name) of the Omada controller, used for management traffic and EAP device communication.
  • The external portal domain name (domain name 2) and its corresponding server IP address, to ensure unauthenticated users can load the authentication page normally.

 

No Need for Additional Allowance:

  • If the domain name 1 (the Omada controller domain name) is only used for management access and is unrelated to the portal authentication process, then it does not need to be allowed in the Access Control for end users. However, you must ensure administrators can access it.
Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:Access Control Configuration for External Captive Portal-Solution
Friday - last edited Friday

Hi  @Rayen_CR 

 

Thanks for posting here.

 

Must Allow:

  • The IP address (or domain name) of the Omada controller, used for management traffic and EAP device communication.
  • The external portal domain name (domain name 2) and its corresponding server IP address, to ensure unauthenticated users can load the authentication page normally.

 

No Need for Additional Allowance:

  • If the domain name 1 (the Omada controller domain name) is only used for management access and is unrelated to the portal authentication process, then it does not need to be allowed in the Access Control for end users. However, you must ensure administrators can access it.
Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
Recommended Solution
  0  
  0  
#2
Options
Re:Access Control Configuration for External Captive Portal
Friday

  @Vincent-TP Thank you for your reply. 
 

So if I understood correctly, my final Access Control list should include:

  • The domain name of the external captive portal

  • The IP address of the external captive portal

  • The IP address of my controller (even if it is already associated with a domain name)

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 56

Replies: 2

Tags

Controller Portal
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.