rmeadows

It would be better and more secure to configure the preauth sso for the product and use an encryption cipher class for it to accept encrypted tokens. You would then need to pass and encrypted token on the url in your scriptlet rather than the username and password in plain text. Thanks.

rest is tied to a jsessionid or session id from the application server. So there is something like a. session...but probably not a persistent open connection to the services.

You are hitting sql validation in the product. You have to either turn it off..or turn on and relax the regex for it. /WEB-INF/classes/esapi Thanks.

This stack shows a report running on the scheduler and the error coming from a query in an input control. You need to have them investigate and find this query in the report. Error executing SQL statement for: db_name_query. as it is having a problem running for some reason against the db by the jdbc driver. From the stack it looks like it may be in an input control. Thanks.

that is the wrong syntax for the parameter name. and type Please look chapter 5.5.2 Built-in Parameters for Query-based Input Controls here in the documentation for correct syntax and types on these parameter names. https://docs.tibco.com/pub/js-jrs/7.9.0/doc/pdf/TIB_js-jrs_7.9_Admin-Gui... The one your are specifying is a collection and meant for use with the $X syntax You want LoggedInUserAttribute_::atribute_name:: syntax and a string value if you want to use $P. Otherwise the string value of a collection may be injected with the [] on it for the collection type. Also make sure you are defining a parameter with these names in the report with the correct. matching type. (Collection, String, etc)

you are probably using a key/cert for filezilla to do the https (or ssl portion). For jasper you will need to import those items into the java cacerts keystore so that you can successfully complete the ssl handshake required when you configure for ftps and the ftps port. Thanks.

that is the wrong syntax for the parameter name. and type Please look chapter 5.5.2 Built-in Parameters for Query-based Input Controls here in the documentation for correct syntax and types on these parameter names. https://docs.tibco.com/pub/js-jrs/7.9.0/doc/pdf/TIB_js-jrs_7.9_Admin-Guide.pdf The one your are specifying is a collection and meant for use with the $X syntax You want LoggedInUserAttribute_::atribute_name:: syntax and a string value if you want to use $P. Otherwise the string value of a collection may be injected with the [] on it for the collection type. Also make sure you are defining a parameter with these names in the report with the correct. matching type. (Collection, String, etc)

add a where statement to your query on the jiuser tables user name field. Where are you running this query and for what purpose (since you will need the current username to inject into the query.

try turning off sql validation in /WEB-INF/esapi/secuirty-config.properties or log the EngineServiceImpl class to see if that is what is cuasing your issue. Thanks.

studio repository explorer is using rest web services on the server. Thanks.

You are running on way too little memory for JRS. For 7.2 from the supported platforms guide these are the requirements for JRS: Minimum system requirements: 2 Core processor, 8 GB RAM, 10GB free disk space Recommended system requirements: 2.5 Ghz multi Core processor, 12GB RAM, 40GB free disk space Please bump your memory to minimum or above. Thanks.

your base context (/jasperserver-pro ..or for you / since it is at root) will redirect to the login page internally. Here is a standard nginx proxy config for jasper at the out of box context and path. Feel free to adjust accordingly. https://community.jaspersoft.com/wiki/nginx-proxy-tibco-jasperreports-server Thanks.

No..you can compile the source and build the webapplication and install the product using buildomatic (WAR file installer that you ar building from source) but the .run file is a linus installer applicaiton. It is not part of the source. Thanks.

Mayber your are using an older applicationContext file? pull the new one from 7.8 unders the samples folder and merge your configuration into it. for this error the constructor arg syntax here is wrong: <constructor-arg index="0" ref="ldapAuthenticationManager"/> and it should be a property as shown below: <property name="authenticationManager"> <ref bean="ldapAuthenticationManager"/> There may be other changes so I would recommend comparing against the 7.8 version under the samples folder and merging in your needed configuration into the newer file. This is a best practice for each new release to which you want to upgrade. Thanks.

you should be able to download a ce version...or the commercial version as a trial on edelivery.tibco.com Please request or speak with a sales associate for further assitance if needed. Thanks.

passwords are not pulled or generated for external authentication. Any code like this would probably not be publicly available either. Are you having osme issue? Make sure if you are clustered you are using the same keystore for your jasper instances. Thanks.

looks like you are missing the server property in yoru auth block. Thanks.

that script is located in the docker material you downloaded form the github. Since the first part of the path is usr/local/scripts I believe it may be your working directory. You need to run the build command and other commands from specific directories. <CONTAINER_PATH>/jaspersoft-containers/Docker/jrs the build command is from this directory after setting up your .env and default_master.properties file correctly. the unpack command is run from the scripts directory...Run cd <CONTAINER_PATH>/jaspersoft-containers/Docker/jrs/scripts and then run ./unpackWARInstaller.sh. If your path is not resolving correctly per these steps you could symlink to the directory containing this script in the github material and folder structure and then run the build so that it finds the script correctly although I also used this material recently without issue. Thanks.

Have you tried setting the https://api.highcharts.com/highcharts/plotOptions.series.dataLabels.allowOverlap property to prevent overlap? I don't think you can get/set that property for each point but maybe for a series with : https://api.highcharts.com/highcharts/plotOptions.series.dataLabels.y unless there is a more point specific category. Thanks.

I beleive spring changed this over from a property to a constructor argument in the bean configuration. You would need to attach your applicationContext file to verify and review. Is this the applicationContext file that you got with this JRS version? Thanks.

If you are trying to inject a profile attribute into a datasource definition in the datasource creation dialog it uses an attribute{} syntax. However, it looks like you are tyring to retrieve them as the built-in parameters that are available in report and input control queries. You will need to uncheck isForPromprting on your parameter if you do not intend for it to have an attached input control on the server otherwise it will be expected that you attach an input control to the parameter. Also, your parameter name syntax should be LoggedInUserAttribute_ <attribute-name> for it to pull the profile attributes from the user. Everything else sounds setup correctly. Please see here in the administrator guide for reference to the built-in parameters that you can define (remember to uncheck isForPrompting for these if you create them in a report for usage) https://docs.tibco.com/pub/js-jrs/7.9.0/doc/pdf/TIB_js-jrs_7.9_Admin-Guide.pdf Chapter 5.5.2 Built-in Parameters for Query-based Input Controls Thanks.

Try adding them to your urls on the calls as a workaround. These should also be able to be passed on any JRS url call.

Do you have any reports using relative dates? Thanks.

try the above with BigDecimal.ROUND_CEILING or set the number of decimal places to 1 so that it rounds at that position. so $V{ RoundUp}.setScale(1,BigDecimal. ROUND_HALF_UP) Thanks.

This is due to a change in EPL repository content. (specifically a python dependency per your output log file). You will need to comment out both yum commands in the each userdata section of the cloud formation template so that the cfn-init is not installed or updated and will rely on what was built into the image as a workaround. Thanks.