shmee
-
Posts
37 -
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 shmee
-
This seems to be fixed in 4.7.
-
There is more to it then just one line. If you read the whole file you will see several lines that need to be uncommented, and configured. Also do not save backup copies of the file in the same location because JasperServer loads all the .xml files in that location. Where are you trying to get your LDAP queries from? Since different LDAP sources have different changes to the file. There are several examples in this forum of people getting this to work, if you look around.
-
Have you tried upgrading to 4.7?
-
I fixed my issue, which was similar, by using a stand alone version of Tomcat 7 (which is the managed version in Ubuntu 12-4), and then doing a WAR installation. And following the upgrade steps from the install guide for using a new DB. It is also important to use the export script from the /buildomatic folder from the old version of JasperServer, so in this case the 4.5 version.
-
It turns out the only way for me to fix this issue was to export my data and then do a upgrade with a new db. I used the upgrade method outlined in the install guide for people not upgrading from version 4.5.
-
When I do an upgrade from 4.5 to 4.7, everything says it installed OK, but when I go to the web page all I get is an Internal Error Has Occurred please contact the Systems Administrator Details: But it lists nothing under the Details. Anyone seen this and able to help? I have attached the imaged of what the screen looks like. Post Edited by shmee at 09/10/2012 18:08 Post Edited by shmee at 09/10/2012 18:08
-
I am glad that you got it working.
-
Is there a hack to fix this?
-
Any updates on this? A hack that I can user maybe?
-
I don't know if you fixed your issue yet but here is my file (with names changed for security of coarse). And I am using Windows 2008R2 and JasperServer4.5.
-
Do you know when the next release is scheduled? Also I used the Validator.EmailAddresses regex for Validation.Email and it seems to be working.
-
No problem here you go. If it helps you let me know.
-
Is there a change log for this project? The one you have only goes to 3.7. It would be handy to know what has changed when we are performing upgrades. Thanks.
-
I foud my issue. There is a slight differance in the two security files so I pretty much coppied my config to new file and it worked.
-
I upgraded our JasperServer from 4.0.0 to 4.1.0 and every thing seemed to work just fine, until I tried to log in with my LDAP. It seems like every release changes something with the Active Directory LDAP. I am using the same applicationContext-security.xml as with 4.0.0 but I am getting errors. Is there something that changed that I should know about?
-
We noticed ours was slow in JBoss as well, and we changed over to Tomcat 6 and it has worked much better.
-
You need to change your config just a little bit. Code:<property name="extraEnvVars"> <map> <entry key="java.naming.referral" value="follow"/> </map><property>You needed to put:<property name="referral" value="follow" />
-
Depending on the type of machines you have at your disposal you could always setup your own SMTP, or at least install Sendmail if you are on linux, since I am guessing you are mostly sending your reports to internal users. That way you are not always at your SMTP providers mercy.
-
Thanks for the tips guys! I was just thinking about how I wanted to audit the JasperServer, so I checked the forum, and this thread got me started. Though it would be much cooler to have built in user and report auditing.
-
I would also check to make sure that you don't need any extra ".jar"s in your web-inf/lib folder, to connect to the database you are getting reports out of.
-
Well the jar that you are looking for would depend on that database you are connecting to and the platform it is running on. Because I also connect to DB2 but on an iSeries server, so the jar I always need to add to lib is jt400.jar
-
Is there a reason you want to use JAAS instead of LDAP? I use LDAP to authenticate against my AD and it works great. It took a little while to get it working but I think it is easier to setup then JAAS.
-
I just figured out my problem!!!! Instead of: <property name="baseEnvironmentProperties"> <map> <entry key="java.naming.referral"> <value>follow</value> </entry> </map> <property> I needed to put: <property name="referral" value="follow" />
-
Thanks.
-
Well if you are not using Active Directory then it should be different. If you look at one of your groups through an LDAP browser then you will that the "cn" is the name of the group and that the people or objects in the group are all listed as "member". That is where those values come from. If you are not using AD then I don't know what your values are or should be, but getting a good LDAP browser will help you out a lot. Though my LDAP auth is still not working so maybe you shouldn't be taking my advice.
