I was wondering if it would be possible to add a feature where one can select as which user to call an ExternalParameter.

To give an example, I use a PowerShell script to monitor DFS Replication Backlog on Windows. The script works fine, but it cannot run as "SYSTEM". It requires a user with administrative privileges to run it.
Obviously I would not want to run the NetXMS service as such a user.
Storing credentials on the system being queries does not seem like a good idea.
Setting up specific user and reconfiguring DCOM and other parts of the system to use a locked down account makes setting up monitoring a very manual process.
Same with setting up a scheduled task on the system (which is what I'm doing right now) to collect the data, dump it into a file and then use NetXMS to read the result.

Being able to call the ExternalParameter with an additional username/password which could be configured inside the DCI would allow this to "just work" straight from a template (except for then manually configuring the credentials per system as required - not sure if that would break the Template/DCI relationship).

Cheers,
Tursiops