bixia.ji
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forum
Events
Featured Visualizations
Knowledge Base
Documentation (PDF Downloads)
Blog
Documentation (Test Area)
Documentation
Dr. Jaspersoft Webinar Series
Downloads
Everything posted by bixia.ji
-
nthapa, the url does not work for me either. The build failure was caused by: java.net.UnknownHostException: mvnrepo.jaspersoft.com
-
I tried to update the file jasperserver-pro/scripts/bower_components/js-sdk/src/common/auth/Authentication.js to handle 200 as success, adding the following code: if (a === "success" && b.status == 200) { result = {success: true}; dfd.resolve(result); return dfd; } [/code] after line 60 if(typeof response === "string"){[/code] Multiple tabs work with the change now. With this change, page refresh would also work without adding logout step following http://community.jaspersoft.com/questions/851277/sso-pre-auth-visualize
-
We are using visualize.js to embed jasper report. When trying to use pre-authentication token for login in, first we ran into problem that refreshing page does not work. By adding logout on event beforeunload, refreshing works now (http://community.jaspersoft.com/questions/851277/sso-pre-auth-visualize). (BTW, this is not ideal way) However if I open the report page in another tab, the new tab would not work due to authentication error until the jasper session expires. I traced the problem to REST api call to http://bjil01:8180/jasperserver-pro/?pp=xxxx. When the api call returns 302, it's treated as authentication success, and when the api return 200, it's treated as authentication failure. Shouldn't http code 200 be treated as user already logged in and thus allow report being shown? 401 is the code to indicate authentication error.
