09-24-2012 01:28 AM - edited 03-10-2019 07:34 PM
the message is
2064 Authentication method is not supported by any applicable identity store(s): Authentication failed
the user is present on AD and testing user in ise is ok
the authentication rule to check in AD is created
policy servers are joined and in green status
if I create an internal user (just for testing) authentication is ok
my authentication sequence is:
mab
mab_ad
dot1x
dot1x_ad
those phones uses eap-md5
i guess there is something to check in AD, can someone help me to solve this?
Solved! Go to Solution.
09-28-2012 10:35 PM
I don't think Active directory supports EAP-Md5.
I will recommend to use EAP-TLS instead. Most Cisco IP phones have builtin MIC certificates which really helps to deploy EAP-TLS
09-28-2012 10:35 PM
I don't think Active directory supports EAP-Md5.
I will recommend to use EAP-TLS instead. Most Cisco IP phones have builtin MIC certificates which really helps to deploy EAP-TLS
09-29-2012 08:11 AM
yes that is true however it supports eap md5 against internal database strange thing...
it won't have been a bad thing if it had the ability to turn over the eap-md5 request in another format like ldap...
thank you!!
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