CaptivePortal Active Directory integration with UserPrincipalName attribute

Mk88_it
Mk88_it Posts: 20  Freshman Member
First Comment Friend Collector Second Anniversary
in Nebula Ideas

Hi,

We would like to suggest you to change the AD attribute used by the Nebula Captive Portal Authentication Server integrated with AD to allow the AD users, from SamAccountName (a very old attribute with only 20 characters without domain suffix) to UserPrincipalName, or… at least, allow us to change it.

Thank You

1
Up Down
1 votes

Active · Last Updated

Comments

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,409  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
    edited November 21

    Hi @Mk88_it,

    Could you share your current scenario with us?

    Zyxel Melen

    Share your feedback through our survey, make your voice heard, and win a WiFi 7 AP!


  • Mk88_it
    Mk88_it Posts: 20  Freshman Member
    First Comment Friend Collector Second Anniversary

    Yes my pleasure,

    We have configured a nebula captive portal using "My AD Server" with "External user Group" for authentication, and everything is working fine for 80% of AD users.

    Currently they are using the AD UPN (nome.surname@domain.xxx) to login to their workstations and all the other connected services. In some situations the UPN is different to the SAM , principally because it is limited to 20 characters. In that situations the users can't login trought captive portal using their mail address (AD UPN)

    If you want more details, you can contact me via PM

Categories

Nebula Tips & Tricks


    Read more

    Nebula Help Center

    EnglishTiếng ViệtРусскийไทย中文（台灣）