Reporter | Фагим Садыков (Фагим.Садыков) |
---|---|
Created | Nov 12, 2018 10:09:28 AM |
Updated | Nov 19, 2018 11:11:38 AM |
State | Wait for Reply |
Assignee | Liubov Dievskaia (Liubov.Dievskaia) |
Subsystem | Workflow |
Type | Support Request |
Priority | Major |
Browser | Any Browser |
OS | Any OS |
Fix versions | Unscheduled |
Affected versions | Unknown |
What steps will reproduce the problem?
- Assume you have an local YouTrack installation with path "https://youtrack.my.com"
- Assume you have an workflow that require communication with some REST commands (reports for ex.) over "https://youtrack.my.com/rest"
- While user is already connected to server and have logon, I try just to
new http.Connection('https://youtrack.my.com').getSync('/rest/reports')
What is the expected result?
- While me (or other user) is already connected to youtrack instance in browser we expect that Workflow 'knows' it and should impersonate or use coockies or somethong like this
and current-user context will be used
What happens instead?
- Workflow works at server site, so it cannot use cookies
- Where is no way to say to
http
module that it'sself-REST-call
- No special api at workflow level to call
my-REST
- Workflow API not covers some aspects of application, but REST does
For now we just can make permanent tokens under special user and hardcode it into Authorization
HEADER, but it's not per-user.
Is where some direct or more convient way to call self-REST from workflows with keeping current user context?