How do you get the JRS widgets to load automatically instead of asking you to log in again?
Accepted answer
Hello Delhi,
Looking at the work item associated to the RFE:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/380154
this has been fixed in CLM 6.0.3: "Added an automatic click of the login link to initiate the no-op login (when the JTS is c-olocated)."
Best Regards
Francesco
3 other answers
we have seen reports of this behavior in support.
It's a reproducible scenario that happens the first time each user logs to the server after a restart, when you click the login button on one widget you are good with all the others.
However the same behavior shows up again roughly after 1 day (even if the server is not restarted in the meanwhile).
This is currently being investigated internally.
Best Regards,
Francesco Chiossi
Comments
Thanks, Francesco! I get this behavior every time I open my browser. I can be on that widget and log in so it shows the widget. Then close my browser and open it back up. Log back into RTC and open that dashboard again and it gives me the log in message again. This is unacceptable to use for my customers. I need widgets that load automatically; thus this renders JRS useless for us. :(
Hi Francesco,
Do we have any work item or APAR where it is investigated?
Hello Krzys,
I have an internal Escalation (sent you the link by mail).
Development has stated JRS uses OpenSocial (OS) gadgets (not widgets) to display information on the JTS dashboard. When a gadget needs to query data from JRS, it uses the OS container API to initiate the OAuth dance resulting in a authorization token that would be used all subsequent requests. However, in the situation described by the log, the OS container (JTS) responds with a HTTP 302 code (a URL redirection). Normally, in a redirection situation, the client would re-request the data using the provided redirected URL. However, in this case, it results in another HTTP 302 response with another slightly different URL. This continues into an infinite loop. In order to mitigate the extricate itself from this loop, the JRS gadget has code to detect this condition and call JTS's /jts/proxy/logout service. After this "logout" occurs, the OS container returns the proper response in the form of a OAuth authorization link and login can proceed. What's observed here is that mitigation process in action. This is working as designed.
This is not an acceptable answer that it is working as designed! This is a defect!! When I am logged into RTC and I go to a dashboard, then it should automatically load the widgets on that dashboard. I should not have to log in again! Is there a defect submitted to fix this? I am currently not using JRS widgets because of this problem. Therefore, this problem is stopping my customer from using the benefits of the JRS report. If there is not a current defect submitted on this, then I would be happy to submit one because this is not an acceptable, normal behavior for loading a widget!!