I am wondering if anyone has come across the following scenario and if so what was your fix:
In some areas of our environment we run NAM on our Win10 workstations to utilize eap-chaining. The machines use ActivClient as the middleware. We have noticed that sometimes when users select their PIV (authentication) certificate to use for authentication in an attempt to map their UPN to their AD account that ActivClient & NAM pass the UPN without the extended string. For example, what I mean by that is if my Sub. Alt. Name UPN is 123456789*121005* (121005 being the additional string) that NAM passes 123456789 to ISE and users are not hitting the proper authz policy because ISE does not see/attempt to map their UPN to AD. We have ran through a lot of tests and will continue to.
Here are the versions of everything:
ISE 2.4p5 (moving to patch 6 soon)
Tested the following versions of ActivClient (184.108.40.206) (220.127.116.11) (7.1.0244)
Any help is appreciated.
A few questions for you.
1. What do you have set for your protected identity pattern in the NAM configuration.xml?
2. Are you allowing NAM to provision PAC files based on the successful authentication? If you disable the use of PAC's does the issue still occur?
3. Is SSO in use?
4. Is this a 4 cert PIV card? Are the users selecting the correct certificate for authentication?