Issue with Connecting to WPA 2 Enterprise when user log in account is different than user that launch the application.

Question

We have a medical device that running on Windows 10 OS LTS 21H2. We have an application that launch under user B context while the log in user is user A. When we are trying to connect to WPA2 Enterprise with username and password as well as using Certificate, we do not see message request coming to the Radius Server.

When we launch our application using the same user as log in user, Radius Server is abled to see and process the request. Per our cybersecurity requirement, we have to stay with design of having log in user with less privilege and under that launch application have more privileges due to cybersecurity requirement.

We are sending Profile XML to Windows using WLAN interface. We feel that the issue might be related to user context where profile xml is created under different user which is different from login user.

Does anyone have any recommendations to address this? Our application is written in C# code and running on Windows 10 OS.

Thank you for your help!

Answer 1

Hello,

 

Thank you for posting in Q&A forum.

To further troubleshoot this issue, please kindly try below steps:

1.Check the GPO setting to see if the RADIUS policy is controlled by the policy.

2.Check if the NPS certificate is used for all users that connect to the NPS server.

3.Check the network profile XML and make sure it's created and applied in the correct user context.

 

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

 

Best regards，

Jill Zhou

 

If the Answer is helpful, please click "Accept Answer" and upvote it.