Thanks for helping, let me try to explan...
Backgroud: I want to develop a web app which displays RQM data, authenticating with OAuth. App is developed with node.js / jQuery.
What I have done: implemented OAuth dance between RQM, node.js and user browser:
- node.js check oauth session -> node.js redirect browser to RQM oauth login page -> user login -> RQM redirect back to node.js -> node.js obtain oauth session and proceed
Problem: defects associated with Execution Results come from RTC (in same jazz server), which needs a separated OAuth session.
To enable OAuth for both RQM and RTC, I thought I may have to do this:
- node.js check RQM oauth session -> node.js redirect browser to RQM oauth login page -> user login -> RQM redirect back to node.js -> node.js obtain RQM oauth session -> node.js check RTC oauth session -> node.js redirect browser to RTC oauth login page -> user login (probably not needed) -> RTC redirect back to node.js -> node.js obtain RTC oauth session
This looks complicated and doesn't seem right, is there a more appropriate way on implementing the OAuth dance between RTC, RQM, node.js and browser?
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.
Comments
Paul Slauenwhite
FORUM MODERATOR / JAZZ DEVELOPER Jan 21 '15, 6:47 a.m.Rophy Tsai
Jan 23 '15, 2:22 a.m.