I wonder why Cisco AnyConnect's NAM module doesn't support ANY key caching methods available in the wild? I've gone through release notes for the latest version 4.5 and was susprised to find out this is still the case!
So, OKC is unavailable, CCKM is unavailable, now I've just tested 802.11r SSID on W10 and guess what? Yes, not connecting even though Native W10 supplicant has no issues with that...
Is it NAM or Fast Secure Roaming then? Can anyone from Cisco explain what's going on and what is the roadmap for key caching methods for NAM in the near future? We'd like to use EAP-Chaning with EAP-FAST, but we'd like to keep our seamless roaming experience, please....
Thanks
