this is pretty self explanatory, we are trying to build extensions that can do things with admin rights (like running certain powershell scripts for example) but we noticed that the python environment run on the LocalService account which doesn’t have admin rights. So our question is this, is there a way to deploy the python environment so that it runs on LocalSystem instead of LocalService?
Can you please elaborate on some of the thoughts behind this decision? Every other Oneagent process is running as NT AUTHORITY\SYSTEM including the old extension process.
There are a few extensions where you need to run as SYSTEM such as when querying a database or listing any IIS related properties. This is even visible in the new IIS Extension available through the Hub where App pools and sites is listed with metrics through WMI, but no relationships between each other.
It was a requirement from our security department. As extension framework 2.0 distributes code, it was important that the code does not run as a privileged user. We were looking into a way to opt out of the more secure method, your product idea will help put that onto the radar again.
@Mike_L ,
Just needed this today, and it worked like a charm!
In the meantime, I checked both the Activedirectory extension and the Citrix extensions, and they are different in the runas code. I opted for the Citrix one, as it seems more recent; can you please confirm if that is the case?