Wireless Access

We recently upgraded our controllers to 8.9.0.3 to accommodate AP635's. In testing we discovered that when connecting to eduroam, the user name was simply "@domain.edu" in the controller. Airwave (8.2.14.1) also shows only the "@domain.edu" portion of the username. Looking in CPPM (6.10.7), we see the complete user name just as we would expect. Users authenticating to other models of access points show the complete username as well.

Other SSIDs that do not use the "@domain.edu" appear to work fine on the AP635.


Any thoughts on what may be causing this?

Please see if this thread might apply to you:  https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=19682

I don't know why the version of ArubaOS would have an effect on that, however...

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Nov 07, 2022 01:40 PM
From: David Wolford
Subject: AP635 and client Username

We recently upgraded our controllers to 8.9.0.3 to accommodate AP635's. In testing we discovered that when connecting to eduroam, the user name was simply "@domain.edu" in the controller. Airwave (8.2.14.1) also shows only the "@domain.edu" portion of the username. Looking in CPPM (6.10.7), we see the complete user name just as we would expect. Users authenticating to other models of access points show the complete username as well.

Other SSIDs that do not use the "@domain.edu" appear to work fine on the AP635.


Any thoughts on what may be causing this?

 What is the practical implication of this ?

Original Message:
Sent: Nov 07, 2022 01:40 PM
From: David Wolford
Subject: AP635 and client Username

We recently upgraded our controllers to 8.9.0.3 to accommodate AP635's. In testing we discovered that when connecting to eduroam, the user name was simply "@domain.edu" in the controller. Airwave (8.2.14.1) also shows only the "@domain.edu" portion of the username. Looking in CPPM (6.10.7), we see the complete user name just as we would expect. Users authenticating to other models of access points show the complete username as well.

Other SSIDs that do not use the "@domain.edu" appear to work fine on the AP635.


Any thoughts on what may be causing this?

No functional implication.  802.1x supplicants allow users to set their usernames as anonymous or basically anything they want to hide their username on the WLC.  The radius server always reflects the correct username, but the WLC would show anonymous or whatever is manually set.  The option in ClearPass would override that supplicant setting and show the username used during authentication.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Nov 11, 2022 08:14 AM
From: Steinar Grande
Subject: AP635 and client Username

 What is the practical implication of this ?

Original Message:
Sent: Nov 07, 2022 01:40 PM
From: David Wolford
Subject: AP635 and client Username

We recently upgraded our controllers to 8.9.0.3 to accommodate AP635's. In testing we discovered that when connecting to eduroam, the user name was simply "@domain.edu" in the controller. Airwave (8.2.14.1) also shows only the "@domain.edu" portion of the username. Looking in CPPM (6.10.7), we see the complete user name just as we would expect. Users authenticating to other models of access points show the complete username as well.

Other SSIDs that do not use the "@domain.edu" appear to work fine on the AP635.


Any thoughts on what may be causing this?