Report Builder - LQE data source error - unauthorized user
We have an LQE data source in JTS that looks fine on its own, but we cannot set it as a data source within Report Builder. When i click Test Connection I get a 401 error. Unauthorized User:
Additional. If I hit the (built-in) refresh button on the datasource page (rs -> data sources) I get a red box with
2 answers
Update:
Changed to Authorisation Jazz Security Architecture SSO, and the gui page all goes 'green' but the log is still kicking off:
[ WebContainer : 21] ERROR integration.reporting.data.query.SparqlQueryRunner - CRRGW5502E Authorization is required. You are not authorized to access the URL: https://............/lqe/sparql.
[ WebContainer : 21] ERROR team.integration.reporting.model.services.Endpoint -
java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained
at com.ibm.ws.webcontainer.srt.SRTServletResponse.getWriter(SRTServletResponse.java:836)
at com.ibm.team.integration.reporting.model.services.Endpoint.testConnection(Endpoint.java:700)
at com.ibm.team.integration.reporting.model.services.Endpoint.doGet(Endpoint.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
....
Any thoughts?
Comments
You should consider contacting support.
I am investigating similar "Unauthorized user" error in Report Builder, but with data warehouse data source. In this environment, this error happens about 1 minute after the login, regardless of what operation is done in Report Builder. Is this the same symptom as yours?
I will keep you updated if I find something new.
So we are not sure, but we have it working (most of the time).
We believe it is related to licensing, but even so we think all the underlying processes are working and we can get the users to work as well (by adding/removing licenses) and logging out and in again. In our case the Authorasation must be using SSO (as this is what is setup)
Conclusion: We have it now working 'enough'
Summary: No underlying processes have a known issue, and most of the time the GUI also works for most admin users and we have a fix when they don't