Hey guys,
Also I would like to check on this.
We are using EAP-TLS (using certificates) for authentication after onboarding. We've added Onboard repository as auth source in 802.1x aruba wireless service as well.
The enforcement policy will be like:
1. If authentication outer method equals EAP-TLS, then enforcement profile is 'already onboarded'
2. If authentication source equals Onboard repository, then enforcement profile is 'already onboarded'
But everytime only 1st condition is successful, 2nd condition is not successful after onboarding also.
CPPM always choosing 'AD' as our auth source not our Onboard repository.
Why is that?
Thanks,
Bharani..