UPN username format fails using EAP-TLS

Unanswered Question
Jul 13th, 2008

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 ([email protected]), and ACS received "cannot get user account controler for [email protected]" from windows database, authentication failed. Any workaround for this?

Can anyone throw some light here?

Thank you.

Lahki

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
scadora Mon, 07/14/2008 - 08:14

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.

Shelly

scadora Tue, 07/15/2008 - 08:10

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.

Shelly

Lucky8888 Tue, 07/15/2008 - 15:39

Not sure what you mean by supplicant.

All the laptops are running XP. Is it possible to change the outer-id for XP supplicant? How?

Thank you in advance.

Actions

This Discussion