This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
i am using .net core 3.1.18 web api hosted in IIS. i have load balancer hosting the api on two windows server. i am writing a file since i need to access the file from from two server i am using UNC path for folder sharing.
i need to access a shared location and i am running the code using WindowsIdentity.RunImpersonated.
apppool is running and Network service and Network service has access on shared location.
i am facing the issues not able to access the path.
i have faced the same issue on .Net 5.
is this feature is not supported in .Net core is there any other design / solution for this scenarion.
"Network service has access on shared location" indicates that you are on the wrong path. https://learn.microsoft.com/en-us/windows/win32/services/networkservice-account Network service is a local account, so computer1\Network Service and computer2\Network Service are different accounts. You need to change the application pool identity to a domain account, and configure UNC path permissions for that domain account instead. You shouldn't use impersonation whenever possible.
even i have tried to access the local folder using UNC and was not able to access while with full path i was able to access.
I have tried Network service and a local account.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Somnath Shukla Could you please share related codes about using WindowsIdentity.RunImpersonated.?
I have created a test demo on my side and I could use the windowsIdentity.RunImpersonated to get the file after I hosted the application on IIS. Besides, if the application pool has the enough permission to access the shared file, there is no need to use the WindowsIdentity.RunImpersonated, the application will use application account by default. I suggest you could try to follow this article to make sure you have set the enough permission.
i have tried but will do again. i hope this is for .Net Core 3.1
This issue has been fixed .Net 5.0.3.
and i will get ported in .Net core 3.1. also, but will take some time.