We deployed ACS 4.0 (NOT ACS SE) and WLAN in our corporate network.
Our ultimate goal is to have each staff authenticated against our AD via ACS.
We managed to get PEAP working successfully, but failed with EAP-TLS.
From the log we noticed that when PEAP is used, ACS forward username to AD in domain-qualified format (domain\user),and authentication is successful.
When EAP-TLS is used, ACS forward username to AD in UPN format (user@domain), and ACS received "cannot get user account controler for user@domain" from windows database, authentication failed. Any workaround for this?
What supplicant are you using? If you can configure it to send the EAP outer-id in a different format (e.g. just "username" or even "anonymous"), then you should avoid this problem. Otherwise, you'll probably need to upgrade to ACS 4.2.
Okay, but your PC still has to have a supplicant. If there's no way to change the format of the EAP outer-id in your supplicant, you'll need to upgrade your ACS. If you have access to bug toolkit, look up CSCsk49811.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...