Creating a Public Dashboard
Accepted answer
The summary of all the answers here is that it would require some kind of authentication to access the data in the CLM/ELM products. It would be possible to use a functional user (similar to the users used by build engines) to create dashboard information. It would be possible to use the same functional user to access the ELM tools to get data using REST/HTML APIs. OAuth and other authentication mechanisms could be used as well, but finally there would have to be some authentication.
7 other answers
Kelley,
I am not sure how to get around the login issue. However read access is for free - if access is allowed at all.
You could create a Guest user with no RTC license. As long as the user has access to the dashboard he should be fine.
Alternatively all users could have their own login to RTC without dedicated RTC licenses assigned. The only issue is displaying the dashboard in your WiKi. I think I read about plans to allow to use RTC Dashboard viewlets in portlets. Again not sure this would allow avoiding the login.
Ralph
I am not sure how to get around the login issue. However read access is for free - if access is allowed at all.
You could create a Guest user with no RTC license. As long as the user has access to the dashboard he should be fine.
Alternatively all users could have their own login to RTC without dedicated RTC licenses assigned. The only issue is displaying the dashboard in your WiKi. I think I read about plans to allow to use RTC Dashboard viewlets in portlets. Again not sure this would allow avoiding the login.
Ralph
What is the best way to create a dashboard on a company wiki without logging in?
Can we use a generic viewer license?
There is currently no way to avoid authenticating with the server. If you feel this is a valid and valuable use case, please file a work item.
In terms of embedding a Dashboard in your wiki, currently the only way to do so would be to use an iframe that embeds the entire web ui (pointed at the Dashboard page of course). We are working on a set of reusable building blocks to deliver in tandem with Dashboards that would allow consumers to create simple widget ensembles for scenarios like this, though I cannot comment on when it will be ready for general use.
Adam Archer
Jazz Web UI Developer
In terms of embedding a Dashboard in your wiki, currently the only way to do so would be to use an iframe that embeds the entire web ui (pointed at the Dashboard page of course). We are working on a set of reusable building blocks to deliver in tandem with Dashboards that would allow consumers to create simple widget ensembles for scenarios like this, though I cannot comment on when it will be ready for general use.
Adam Archer
Jazz Web UI Developer
Unfortunately we don't offer anything that would help you achieve that at this time. In the current release we are starting to look at surfacing more of our Viewlets as OpenSocial gadgets. This would lower the barrier of entry to embed them in non-dashboard web uis, but there would still be some legwork required in embedding them. Also, I'm not sure we have any plans to port any of the charting widgets.
Adam Archer
Jazz Web UI Developer
Adam Archer
Jazz Web UI Developer
Can we not write our own open social gadget using the JAZZ restful API? Is there no way to authenticate the uses in the Javascript code of the gadget?
This would be a killer feature to integrate Jazz/RTC data into our Confluence wiki, another reason not to continue with our Jira strategy.
Paul
This would be a killer feature to integrate Jazz/RTC data into our Confluence wiki, another reason not to continue with our Jira strategy.
Paul
Unfortunately we don't offer anything that would help you achieve that at this time. In the current release we are starting to look at surfacing more of our Viewlets as OpenSocial gadgets. This would lower the barrier of entry to embed them in non-dashboard web uis, but there would still be some legwork required in embedding them. Also, I'm not sure we have any plans to port any of the charting widgets.
Adam Archer
Jazz Web UI Developer
It would be possible to write an opensocial gadget using the jazz rest APIs, but the user would still need to authenticate themselves for each browser session within the gadget using oauth. Otherwise, you won't have an authenticated user with which to call the APIs. Also, you would need to have an opensocail gadget container available to host it in your wiki. I'm not sure about the details of how you would do that.
Adam Archer
Jazz Web UI Developer
Adam Archer
Jazz Web UI Developer
