Cisco Bug: CSCsy90822 - ACS 5.0 begins every EAP session with an EAP ID of 0
Feb 22, 2014
- Cisco Secure Access Control Server Solution Engine
Known Affected Releases
Symptom: Avaya IP phones fail to authenticate to ACS 5 with 802.1x even though a success is passed back from ACS. ACS 5 begins every new EAP session with an identifier of zero. It will increment the identifier with every new EAP challenge, however in the event of EAP-MD5, there is only one challenge, so every EAP session has an identifier of zero. Avaya phones cannot parse the 0 value correctly. ACS 4.x started at 1 and incremented this identifier with each new EAP session. Conditions: ACS 5.0 using EAP-MD5 authentication with Avaya IP phones as the supplicants.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases