Guest

Preview Tool

Cisco Bug: CSCsz69843 - ACS SE - Problem when default proxy is updated with different ACS server

Last Modified

Mar 15, 2016

Products (1)

  • Cisco Secure Access Control Server for Windows

Known Affected Releases

4.2(0.124)

Description (partial)

Symptom:
  
No proxy to default proxy servers.
  
Conditions:
  
ACS SE 4.2.0.124.10 configured with 3 entries in the proxy distribution table:
 
 @domain1 > proxy to ACS itself
 @fake.domain > proxy to 2 Linux Radius servers
 @domain2 > proxy to 2 Linux Radius servers
 
If we remove the second dummy entry to proxy requests for @fake.domain, ACS
stops forwarding the access-challenges from the Linux Radius servers to the AAA
client, when we try to authenticate users from domain2.
If we keep the second entry for the non-existing @fake.domain, then
access-challenges are correctly forwarded by ACS from the Radius servers to the
AAA client, when authenticating users in domain2.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.