crafty

JasperServer Pro 3.7.1 On the login_mt.jsp page, if a "flag" is set I want to display certain information to the user. Questions: 1) What is best place to set the flag? 2) Are the any examples of this this to look at?

Using JasperServer Pro 3.7.1I am using Active Directory as an external authority. The LDAP module com.sun.security.authmodule.LdapLoginModule is being used.I would like to log and return more detailed information to the user when authentication fails. For example, if the account has expired, I would like "Account Expired" returned to the user and logged. Currently, JasperServer just reports "Invalid Credentials Supplied. Could not login to Jasper." In the log file you just see "Authentication event AuthenticationFailureBadCredentialsEvent"What section of JasperServer code handles the LDAP login exception? I believe more exception information is available from the login module because if I use an LDAP browser, I see:Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903AA, comment: AcceptSecurityContext error, data 701, v1771"data 701 corresponds to "account expired" per this link:http://wiki.service-now.com/index.php?title=LDAP_Error_Codes

I inherited some custom code (see attachment) that has been running fine on JS pro 2.1. I am trying to migrate to JS pro 3.7. In 2.1, the code uses import com.jaspersoft.jasperserver.api.engine.jasperreports.util.JExcelApiHyperlinkProducerFactory. I am having a difficult time discovering what the equivalent class would be in 3.7 since JExcelApiHyperlinkProducerFactory seems to have been discontinued. The function of the class is to run a report to generate a "pageless" Excel report. Actually it is a document with a single page. Is there any sort of mapping of old classes to new classes for JasperSoft? I did not find what I was looking for in the API documentation. Perhaps I overlooked something. Any help is appreciated. Eric

I got the following reply from JasperSoft support: =========== It seems that jaas can return a principal that is a string. But com.jaspersoft.jasperserver.api.metadata.user.service.impl.MetadataAuthenticationProcessingFilter expects that the principal will always be an instance of UserDetails. MetadataAuthenticationProcessingFilter needs to be more flexible so that it correctly handles the case where the principal is a string. Workaround: create your own class for use with JIAuthenticationSynchronizer. Therefore we don't use the normal line in applicationContext-security.xml: <bean id="JIAuthenticationSynchronizer" class="com.jaspersoft.jasperserver.api.metadata.user.service.impl.MetadataAuthenticationProcessingFilter"> Instead we use this: <bean id="JIAuthenticationSynchronizer" class="yourpackage.jasper.auth.MetadataUserAuthFilter"> In case it's interesting, this guy seems to have solved the same issue: http://forum.springframework.org/showthread.php?t=41588 ================== Note: This issue is resolved in JasperServer 4. I was able to login using JAAS and AD with no problems. I am not sure about the versions between 2.1 and 4.

I was able to resolve the issue by specifying the managerDn differently in the initialDirContxtFactory bean. Instead of property name="managerDn"><value>cn=admin,dc=company,dc=test</value></property> use: <property name="managerDn"><value>admin@company.test</value></property> Note: I was using ActiveDirectory Server 2008. I am not sure if this works for other versions. Post Edited by crafty at 02/24/2011 18:33

Configuration: JasperServer 2.1 (Acegi 1.0.1) I am trying to change my webapp to authenticate against Microsoft Active Directory. My external user is cn=admin,cn=users,dc=maxview,dc=test I am having trouble properly configuring DefaultLdapAuthoritiesPopulator. I was trying to use this resource as a guide even though it is for a newer version of JasperServer. http://www.google.com/search?q=jasper+external+cookbook&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a I also looked at: http://www.eng.utah.edu/~ryant/mediawiki-1.15.4/index.php/Gabriel_Mongefranco%27s_Guide_to_LDAP_Authentication_for_Jasperserver My current error is: 17:25:06,270 WARN LoggerListener,http-8082-1:55 - Authentication event AuthenticationFailureBadCredentialsEvent: admin; details: org.acegisecurity.ui.WebAuthenticationDetails@12afc: RemoteIpAddress: 131.199.122.226; SessionId: E92EEFEB55B39282FA1EE321B6959CEE; exception: Bad credentials (I know that I am typing the correct login/password so I am guessing that I have configured something improperly.) The application-Security.xml is attached. I would appreciate some guidance.

I want to use JAAS because other (non Jasper) applications from my system use JAAS and it will allow me to reuse some code.

configuration: Jasperserver Professional 2.1, tomcat 6.0.26, Java 1.6 I am trying to configure jasperserver to authenticate via Active Directory using JAAS. I just wrote a simple (non-production) authorityGranter class (see attached) that grants role_adminstator to everyone. The class appears to be getting called and run from applicationContext-security.xml (also attached). The login page comes up and the logfile appears to show a "successful" login but the following error is displayed in jasperserver.log: 11:49:18,691 WARN JILicenseFilter,http-8082-1:104 - License OK. JasperServer Professional Commercial license with no expiration date. 11:49:35,113 WARN LoggerListener,http-8082-2:55 - Authentication event AuthenticationSuccessEvent: admin; details: null 11:49:35,129 WARN LoggerListener,http-8082-2:55 - Authentication event InteractiveAuthenticationSuccessEvent: admin; details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 192.168.188.44; SessionId: 4B19AC6948595A773DCF71E5EEA531E8 11:49:35,175 ERROR JSErrorPage_jsp,http-8082-1:339 - java.lang.NullPointerException at com.jaspersoft.jasperserver.war.control.LoginController.getBestHomeURLForUser(LoginController.java:174) at com.jaspersoft.jasperserver.war.control.LoginController.loginSuccess(LoginController.java:147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) The stdout from tomcat log is also attached. It appears to show that authentication succeeded and my AuthorityGranter code does get run. Can some explain what the subsequent error means and what I need to do to resolve it. Thanks.

Thanks for the reply. I need clarification on one part of your answer. I need to know the Spring Security (not the spring framework version) version used by jasperserver 4. Jasperserver 3.7.0 appears to be using Spring Security version 2.0.4. Eric

I have a project that is currently using jasperserver pro 2.1. We are considering migrating to JasperServer 4. I have several questions: 1) What version of Spring Security is used in JasperServer 4? 2) Are there migration steps for getting from 2.1 to 4? I am trying to get an idea of the amount of effort required. What are the pitfalls, things to consider, etc.

I have a web application built with JasperReports professional 2.1, which uses Spring Security (formerly ACEGI 1.0.1) for authentication. I have a design goal of a single point of authentication configuration for multiple Java applications, some standalone and some web apps. I think I need to reconfigure the application to use ACEGI to configure JAAS using the interface javax.security.auth.login.Configuration. I have looked at the Spring Security JAAS samples using a flat file to configure JAAS. Are there any working examples of setting up JasperReports to use a custom javax.security.auth.login.Configuration rather than a flat file?