Jump to content
We've recently updated our Privacy Statement, available here ×

javiiglesias

Members
  • Posts

    4
  • Joined

  • Last visited

javiiglesias's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Thanks lschroth! It works! This is the URL successfully working: jdbc:sqlserver://myHost:1433;databaseName=myDatabase;integratedSecurity=true; Now I have the reports stored in my server connecting to the database with integrated security, but the problem is that this is not what I really wanted to get. Now, all the users are accesing my server and they are ALWAYS accesing to the data with the server's credentials (which are unique) . That is not what I really wanted to get. I need to get each user accesing to the reports and connecting to the database with their own user credentials, not with the server user credentials. I got this in the past with Windows technology (Reporting Services). Is there any way to get the same in JR? Thanks, again! Javier
  2. Hi, We need to implement a report using a database connection (to a MS SQL Server database) using Windows Integrated Security, automatically using the credentials of the Windows user, without being obligued to use an specific user and password. When you desing a report, user and password to connect to the database are mandatory, but I need to dynamically take the windows credentials. Is this possible in Jasper Reports? How can we indicate this? Thanks! Javier
  3. We have discovered a strange behaviour visualizing reports in Jasper Server when using direct links to the reports in the repository. We are successfully using links in this way: http://localhost:8080/jasperserver/flow.html?_flowId=viewReportFlow&reportUnit=%2Freports%2Fcobre%2FProducts The problem appears only when we try to hide the JS banner in top of the screen, using the additional parameter "&decorate=no" in the URL. In this case the date picker combos for the report parameters don't work. It only fails for parameters of type "Date", the combos don't allow you to choose a certain date. It seems like a bug. How can we solve this? Thank you very much! Javier Post Edited by jiglesias at 12/30/2010 11:42
  4. We use Jasper Server 3.7.1 Community Edition and we are experiencing problems trying to integrate security in our application. We use JBoss 4.2.3, deploying our application as an EAR and the Jasper Server as an independent war. We are using JAAS for security, we have defined this JAAS authentication policy to authenticate against an LDAP (in login-config.xml file): <application-policy name ="cobre-admin"> <authentication> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</module-option> <module-option name="java.naming.provider.url">ldap://127.0.0.1:389/</module-option> <module-option name="java.naming.security.authentication">simple</module-option> <!-- Rebind as a user with search priviledges for the role queries <module-option name="java.naming.security.principal">cn=Root,dc=jboss,dc=org</module-option> <module-option name="java.naming.security.credentials">secret1</module-option>--> <module-option name="principalDNPrefix">uid=</module-option> <module-option name="principalDNSuffix">,o=airtel.es</module-option> <module-option name="rolesCtxDN">o=airtel.es</module-option> <module-option name="uidAttributeID">uniqueMember</module-option> <module-option name="matchOnUserDN">true</module-option> <module-option name="roleAttributeID">cn</module-option> <module-option name="roleAttributeIsDN">false</module-option> <module-option name="searchTimeLimit">5000</module-option> <module-option name="searchScope">ONELEVEL_SCOPE</module-option> </login-module> <!-- Needed to propagate the authentication info to the components called by the tests (mainly EJBs) --> <login-module code="org.jboss.security.ClientLoginModule" flag="required" /> </authentication> </application-policy> This LDAP authentication works fine for our web application, but the problem appears when we try to use the same JAAS realm for the Jasper Server war. We configure JS to use the same policy but it doesn't works in the expected way. The idea is to integrate our web application to Jasper Server reports by linking to Jasper Server repository elements, without having to authenticate twice, using JAAS and the Single Sign On valve mechanism provided in JBoss. How can we indicate JasperServer to use our JAAS realm? Is this possible? I have read is possible, but can't get it. Where can I find some example? If not, how can we get the same SSO result? I have checked that JR uses ACEGI, but I can't find the connection for the moment between ACEGI and JAAS. Thanks a lot in advance! Javier
×
×
  • Create New...