1
0
-1
1 answer
- 10-1
Hello Yaakov,
At the moment is possible to this in the incoming script:
syncRequest.proxyUser = "userKey"
This would make that all the issue updates would be executed by the user that was set there.
Unfortunately this doesn't cover the user used to retrieve information of the issue (and run the JQL from the triggers) which at the moment is always the proxy user configured in general settings. We will be evaluating the inclusion of this feature.
Best regards,
Juan
Add your comment...
Hi,
I want to use different proxy user for different connections (because of security reasons), is it possible to set it via the sync rules?
Hello Yaakov Shamii
Is it for accessing issues or for updating issues (or both)
Hi Francis Martens (Exalate) ,
it's for both.
After reviewing - there are a couple of methods allowing to impersonate the behavior (such as creating comments and such), but the product currently only supports a single proxy user.
This is something for the product backlog.
What is the security concern you want to address, such that we got the specs right?
Francis Martens (Exalate)
We just don't want to have one user with access to all projects.
A proxy user per connection would fit the requirement, and if not specified, fall back to the default proxy user?
yes, that would be great
ok - added.
We first have a couple of other things to address (such as native sprint sync and more), but we'll get to it going further.
Thanks Francis Martens (Exalate)