Wireless Access

7005 controller running ArubaOS 8.4.0.2. New IAP-315 and prior IAP-215s deployed. iOS 12.x clients.

 

Trying to deploy a farily simple WPA2-PSK SSID after upgrading from 6.5.x ArubaOS.

 

WPA2-PSK SSID deployed prior to upgrade behaves as expected - no captive portal is triggered or displayed.

 

Newly deployed SSID, trying to rely on WPA2-PSK for some reason causes client to display captive portal websheet in iOS (and macOS) ui. Access > Default Role = logon (identical to pre-upgrade WPA2-PSK SSID).

 

Unsure why the captive portal is being triggered. Have deleted and created new SSIDs configured identically - no change in client behavior. Have tried different AP groups, wondering if new IAP-315 might be to blame...?

 

Any thoughts on how to stop the captive from triggering would be much appreciated.

Isolated the latest, new WPA2-PSK SSID to AP group with *only* previously deployed IAP-215s. No change in behavior - captive portal web sheet still triggers on client after successful authentication.

Also created new, open SSID in ap group limited to IAP-315. Same result. Client joins. But captive portal web sheets still presented. Thinking it might be access role related...

You shout set the initial role in the aaa profile to authenticated. Logon role will trigger a captive portal page.

Also check with show user-table which role is assigned to the user/device

Seems to have done the trick.

 

Thanks so much.