03-17-2010 07:35 PM
We were doing some testing on RAP-2.
I connected my laptop to this 802.1x SSID on AP61, then connected my laptop to other SSID RAP-5.
My client user role changed from "customized role" to a 'Denyall" role.
And this "denyall" role was stuck on my client, even after I disconnected to the SSID.
This "denyall" role could not be disconnect on the Aruba WebUI (monitoring > Clients).
Anyone had this experience before?
After a few hours, another user connected via 802.1x and got this "firstname.lastname@example.org" authentication error on the IAS, and user authentication failed on Aruba controller.
Solution for "denyall" client:
We withdrawn the "denyall" client by applying blacklisting, and took the client out from blasklisting after that.
03-18-2010 08:55 AM
Director, Strategic Account Solutions
03-18-2010 10:35 AM