ACS v4.1 integration with Aruba controller

[m-avramidis]

Help! If I use ACS 3.3 have no problem to connect the Aruba controller via Radius to the ACS. When using ACS 4.1 it is not (?) possible, suspect that this has something to do with the "Key Wrap" line in AAA Client on the 4.1. How to "translate" or overide that line?

Question 2: after configuring PEAP on the ACS, how to deny Aruba from "answearing" - the clients- with the wrong certifikate? It keep sending its own default certificate to my clients...

Wrong forum? Maybe...but can not find any answears on the Aruba support site.

[carenas123]

It sounds as though the controller may be stripping the domain from the

authentication sent to ACS (there may be other explanations for what is

occurring

1. Turn the logging level on the ACS to full

This is accomplished by going into system configuration, service

control, setting the logging level to full, then restarting services.

2. Run a test with the problematic Aruba controller

3. Run the same user in a test with one of the working controllers.

I hope it will help you for troubleshooting