A certain site UOS terminal 802.1X authentication fail, Windows terminal normal

A customer at a certain site reported that terminals running UOS could not pass 802.1X authentication, while normally functioning Windows terminals could connect without issues.

Debug the 802.1X authentication process for UOS and Windows terminals using the following command:

debugging  wlan access-security all 
debugging  dot1x all  
debug radius all  

It was found that the terminal authentication username of UOS does not carry the customer's domain address suffix, while Windows computers have the domain suffix, and the domain is not automatically filled by AC, as shown below:

Windows terminal

UOS terminal

Not related to the device side. On the terminal side, investigate the reason why the host username does not carry the domain suffix.