Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 6 of 6
  1. #1

    Omada: Local users are NOT defined within a portal.

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Offering this info for those that are just starting to plan or build out there wireless network.

    Just discovered that local user logins are not defined with a portal. That is rather disappointing. I guess I missed that in the manuals but then the manuals are not 100% up to date with the latest hardware/firmware/software versions.

    I plan was to have pools of users separated into SSID/portal groups. It looks like that is not possible so now I'm looking into either building out a RADIUS server or creating my own external portal.

    The fun just keeps coming!

  2. #2
    Hi,

    Local user is a new function of Portal, what do you mean "Local user logins are not defined with a portal"?

  3. #3
    Quote Originally Posted by Tammy007 View Post
    Hi,

    Local user is a new function of Portal, what do you mean "Local user logins are not defined with a portal"?
    I have two user groups; Staff and Teams. I need each group to be isolated to their own VLAN.

    Example:
    - Create an SSID called "Staff" with a VLID of 72.
    - Create a portal called "Staff-Portal" bound to the "Staff" SSID.
    - Set the portal to use Local User authentication.
    - Create users for the "Staff-Portal".

    - Create a second SSID called "Teams" with a VLID of 86.
    - Create a second portal called "Teams-Portal" bound to the "Teams" SSID.
    - Set the portal to use Local User authentication.
    - Create users for the the "Teams-Portal".

    With the above set-up, "Teams" users will be allowed to login to the "Staff" VLAN. "Staff" users will also be allowed to login to the "Teams" VLAN. All Portals share a single Local User database.Not sure if this is an oversight or a bug.

    Regardless, it would be a valuable feature and can't be that hard to implement. All that is needed is to add a portal identifier to the Local User record. For "backward compatibility" it can be implemented to allow association with multiple portals and make "All Portals" the default. Though I sincerely doubt anyone would want users to log into more than one Portal with the same credentials.

  4. #4
    Hi,

    For now, Local User portal function of Omada Controller just share same Local User account. We will add your suggestion in our improvement suggestion list, thank you for your feedback!!

  5. #5
    Quote Originally Posted by Jonas_TP-Link View Post
    Hi,

    For now, Local User portal function of Omada Controller just share same Local User account. We will add your suggestion in our improvement suggestion list, thank you for your feedback!!
    Thank you! This is the reason I chose to use 100% TP-LINK equipment in my solution - you actually listen your customers!

  6. #6
    While you are at it, could you look at adding the portal identity to the Voucher portal also? The reason is the same, each portal using Voucher authentication should have a separate pool of vouchers.


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.