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

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

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.

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.

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.

Maps Pro uses Google Maps. TIBCO Maps uses TIBCO GeoAnalytics Maps, which you need a separate license for.

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.

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

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

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

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

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?

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?

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

You can schedule reports to be sent by mail.