06-24-2020 01:39 AM
Hi there, I have encountered a very strange problem with ISE over the last couple of weeks.
We are currently running ISE as our BYOD solution with AD auth as credentials for users. The current version we are running (a 2.4 install) has been running like a dream for the last couple of years we have had it.
A small handful of users (7-8, all range of devices) seem to be having issues connecting to WiFi after registering their devices with ISE through our registration portal. Once devices are registered, and they then attempt to connect to WiFi SSID to gain access, their credentials are being rejected.
Having looked through the ISE logs, I can see at the very last step, the devices are being rejected connection with the error message '12322 PEAP failed SSL/TLS handshake after a client alert'. I notice that credentials registered by the user changes to 'USERNAME' (all caps) automatically in ISE, which seems to be stopping users from authenticating using their AD credentials.
Very strange, as we have only seen this problem crop up in the last couple of weeks after almost 2 years of running ISE with no issues.
Any ideas as to what might be causing this would be greatly appreciated :)
Solved! Go to Solution.
06-24-2020 08:50 PM
The credential showing 'USERNAME' is likely a result of the default disabled setting for 'Disclose invalid usernames' in the Administration > System > Settings > Protocols > RADIUS page. This is a result of the username not being found in the respective identity store.
Enabling the setting will show the true credential in the log, but this would not be the root cause of the failure. You would need to investigate further to find the root cause (try an AD lookup using the Test User tool, check certificate trust on the client side, check certificate expiry, etc).
03-01-2021 12:14 PM
We had a similar issue with Android, we resolved it by modifying the clients. When adding the network (Settings app, select Network & Internet, then select Wi-Fi.) under "CA certificate" select "Use system certificates" then type your domain.
06-24-2020 08:50 PM
The credential showing 'USERNAME' is likely a result of the default disabled setting for 'Disclose invalid usernames' in the Administration > System > Settings > Protocols > RADIUS page. This is a result of the username not being found in the respective identity store.
Enabling the setting will show the true credential in the log, but this would not be the root cause of the failure. You would need to investigate further to find the root cause (try an AD lookup using the Test User tool, check certificate trust on the client side, check certificate expiry, etc).
03-01-2021 12:14 PM
We had a similar issue with Android, we resolved it by modifying the clients. When adding the network (Settings app, select Network & Internet, then select Wi-Fi.) under "CA certificate" select "Use system certificates" then type your domain.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide