Jump to content
Changes to the Jaspersoft community edition download ×

elizam

Members
 View Profile  See their activity

  • Posts

    668

  • 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 elizam

  1. elizam
    as of JRS 7.5, the server generates a unique key when it is installed. Key management is described in the security guide. There are ways todo this in earlier versions,but I see they are not well documented. If you can update to 75, that might be the best solution. https://community.jaspersoft.com/documentation/tibco-jasperreports-server-security-guide/v7/key-and-keystore-management
  2. elizam
    The best I can think of is to create a attribute, then use that for your schema in the domain. Attributes are explained here: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v750/managing-attributes Using attributes for schemas is somewhere in here: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-user-guide/v750/data-management-tab
  3. elizam
    You can force an update from the data warehouse by going to the "kebab" menu (three dots), select Change Data Source and then pick the same data source. Not a shining example of intuitive UI.
  4. elizam
    JSS now has the ability to create a data adapter that connects to a web service, no plugin needed. Here's a JSON example: https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v750/connecting-web-service-using-json-data-adapter XML is similar.
  5. elizam
    You cannot assign roles through the Jasper interface and have them stick for external users. The only roles a user can keep are ones generated through the external authentication process. You need to set up assignment of admin roles in your application context file.
  6. elizam
    Maps Pro uses Google Maps. TIBCO Maps uses TIBCO GeoAnalytics Maps, which you need a separate license for.
  7. elizam
    You need to define roles in the application context file and set the rules that map information from your LDAP to roles JRS. The role will be created the first time a user with that role logs in. It's a good idea to create test users for each role first so that you can set up the role permissions and make sure they are working as expected before going live. Role permissions can't be set in the application context file.
  8. elizam
    I believe so, unless you are using a feature that is deprecated for some reason. If you have any problems, you can change the version of JasperReports you use to compile reports as described here: https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v720/setting-compatibility-earlier-versions-0
  9. elizam
    If you just want to get all the users out of LDAP, you should look at the Authentication Cookbook: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-authentication-cookbook/v720/introduction
  10. elizam
    Have you already tried the steps in these sections and they didn't work? https://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v720/customizing-menus
  11. elizam
    the code was changed in 7.1, but it didn't get into the documentation. Use the updated configuration in the 7.2 Ultimate Guide: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-ultimate-guide/v720/sample-configurations
  12. elizam
    In the documentation, TIBCO JASPERREPORTS® SERVER ULTIMATE GUIDE RELEASE 7.1 section 6.3.3 "Sample Configuration for Failover", it lists web.xml as the first part of the configuration before configuring server.xml. The problem is that we cannot find RequestContextListener class in web.xml file in JRS 7.1 deployment. "Locate the listener of class RequestContextListener and replace it with the listener of class TolerantRequestContextListener". It looks like JRS 7.1.0 dropped the following in web.xml file. How do I resolve this error?
  13. elizam
    Why can't jasper query the database directly? Normally if you have a JDBC driver you can retrieve info from a database. Is that a requirement on your side?
  14. elizam
    in 7.2, they upgraded Spring Security to a new version. It is suggested that you reimplement your external auth using the new files as a base. An overview is here: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-upgrade-guide/v720/changes-72-may-affect-your-upgrade
  15. elizam
    You can schedule reports to be sent by mail.
  16. elizam
    I searched through the Security Guide and can't find the reference you mentioned. Can you post the specific text you mean? Users should not change their password via JRS, because the password is coming from LDAP. I doubt a password change through JRS would work. They should be able to change their LDAP password via LDAP.
  17. elizam
    We don't have the resources to test every possible upgrade path, so we limit the officially supported upgrades. This bug indicates that the direct upgrade likely no longer works: https://community.jaspersoft.com/questions/1114551/migration-jasperreports-server-5-7
  18. elizam
    https://community.jaspersoft.com/wiki/how-extend-jasperreports-servers-functionality-aws also section 2.5 in the user guide fot Jasper AWS
  19. elizam
    That's a SQL Server exception, not a Jasper exception. It's coming from your database. Google offers this discussion on StackExchange: https://stackoverflow.com/questions/23887529/the-incoming-request-has-too-many-parameters-the-server-supports-a-maximum-of-2
  20. elizam
    Have you put the chart in the Details band, by any chance? Aggregate elements, like charts, should go in the Summary band.
  21. elizam
    You cannot do a direct upgrade from 5.x to 7.1. You need to go through 6.4. https://community.jaspersoft.com/documentation/tibco-jasperreports-server-upgrade-guide/v71/upgrading-56x-or-earlier-0
  22. elizam
    Are you trying to use your AWS license on a non-AWS instance, by any chance? Because the license will only work on AWS.
  23. elizam
    What version are you using? A frame should stretch vertically according to its contents. https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v71/using-frames-0
  24. elizam
    Do you have a default bundle, balance.properties? I think that's required.
  25. elizam
    What's going on here is that external accounts take their roles from the LDAP authentication setup, not from the assignment by the admin. Your admin is assigning within JRS, and then the minute the person logs in, the authentication process looks at their permissions from the external authentication process and overrides the manual setting. This is to ensure that you are managing roles in a single place. The documentation on creating admin users is here: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-authentication-cookbook/v71/mapping-roles-system-roles
×
×
  • Create New...

© 2024 Cloud Software Group,
Inc. All rights reserved.

Products

Explore