# Impersonateusername parameter is being ignored

**URL:** <https://discuss.workflowgen.com/t/impersonateusername-parameter-is-being-ignored/1407>\
**Category:** Development\
**Created:** [June 18, 2019, 1:17pm UTC](https://discuss.workflowgen.com/t/impersonateusername-parameter-is-being-ignored/1407 "2019-06-18T13:17:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jianan.hsu](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/jianan.hsu/32/411_2.png) [@jianan.hsu](https://discuss.workflowgen.com/u/jianan.hsu)\
**Post date:** [June 18, 2019, 10:20pm UTC](https://discuss.workflowgen.com/t/impersonateusername-parameter-is-being-ignored/1407/2 "2019-06-18T22:20:28Z")

</div>

Hi,

I just tested on the latest version. The `impersonateusername` parameter does work fine.

Make sure the username of the person using the impersonation is defined in the WorkflowGen main web.config’s parameter `ProcessesRuntimeWebServiceAllowedUsers` as indicated in the article [Web Services API: User Impersonation with ImpersonateUsername parameter](https://discuss.workflowgen.com/t/web-services-api-user-impersonation-with-impersonateusername-parameter/319/3).

e.g. `<add key="ProcessesRuntimeWebServiceAllowedUsers" value="wfgen_admin" />`

In this example, `wfgfen_admin` can impersonate `jsmith` when specifying `impersonateusername=jsmith` in the URL.

---

_[View the full topic](https://discuss.workflowgen.com/t/impersonateusername-parameter-is-being-ignored/1407)._
