03-05-2022 10:36 AM
Solved! Go to Solution.
03-08-2022 09:20 AM
Hello,
I think this will work if the credential is stored on NAC in the local password repository. With MsChapv2 that we use for 802.1x authentication the challenge hash must be sync'd between AD and the NAC, that was the client uses the same challenge hash for the username/password that the AD does.
With Chap I don't think there is a mechanism to sync these hashes from AD to NAC, which is why we need the clear-text password at the NAC to use it with the challenge hash supplied by AD.
Which protocols have you tried at this point?
If you have NTLM authentication set can you also confirm you have successfully joined the AD and that winbindd is running with correct trust secret?
test_wbinfo -s /opt/nac/radius/raddb/smb.* -t
Thanks
-Ryan
03-08-2022 09:20 AM
Hello,
I think this will work if the credential is stored on NAC in the local password repository. With MsChapv2 that we use for 802.1x authentication the challenge hash must be sync'd between AD and the NAC, that was the client uses the same challenge hash for the username/password that the AD does.
With Chap I don't think there is a mechanism to sync these hashes from AD to NAC, which is why we need the clear-text password at the NAC to use it with the challenge hash supplied by AD.
Which protocols have you tried at this point?
If you have NTLM authentication set can you also confirm you have successfully joined the AD and that winbindd is running with correct trust secret?
test_wbinfo -s /opt/nac/radius/raddb/smb.* -t
Thanks
-Ryan