If you see a 'Failed to classify request to service', check the attributes from Access Tracker once they come in versus the Service's Rule conditions.
This Service classification is 'ClearPass basics', so it may be good to check with your Aruba partner, or Aruba Support to get you going.
eduroam is using the same SSID ('eduroam') everywhere... So also check that you are broadcasting the SSID with that name, and all lower-case.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Jul 07, 2021 06:46 AM
From: Peter Gaughran
Subject: Failed to classify request to service - from a newbie!
I've recently started using Clearpass, and trying to get a grasp on why some of our external users cannot connect to eduroam, when others can. Other than the obvious "Authentication failure", the rest are "Failed to classify request to service", but I'm unsure where to start; given they're attempting to auth externally, isn't the issue that the SSID doesn't match down to the other institute? But then I'm at a loss as to how the requests make it back to us at all.
------------------------------
Peter Gaughran
------------------------------