rusty.ross

The reason I don't think that approach will work is that some users are members of both families of groups, and I need to be able to map those users to all the roles for which they are a group member.

I am seeing an LDAP issue in JRS 5.5. LDAP (Active Directory) authentication is configured and working as expected. LDAP external roles mapping is configured and (mostly) working as expected. Here is the relevant config on that: <bean id="ldapAuthenticationProvider" class="org.springframework.security.providers.ldap.LdapAuthenticationProvider"> <constructor-arg> <bean class="org.springframework.security.providers.ldap.authenticator.BindAuthenticator"> <constructor-arg><ref local="ldapContextSource"/></constructor-arg> <property name="userSearch" ref="userSearch"/> </bean> </constructor-arg> <constructor-arg> <bean class="org.springframework.security.ldap.populator.DefaultLdapAuthoritiesPopulator"> <constructor-arg index="0"><ref local="ldapContextSource"/></constructor-arg> <constructor-arg index="1"><value>OU=Internal</value></constructor-arg> <property name="groupRoleAttribute" value="cn"/> <property name="groupSearchFilter" value="(&(objectClass=group)(member={0})(|(cn=ABC-*)(CN=XYZ-*)))"/> <property name="searchSubtree" value="true"/> <!-- Can setup additional external default roles here <property name="defaultRole" value="LDAP"/> --> <property name="defaultRole" value="ROLE_LDAPUSER"/> </bean> </constructor-arg> </bean> The problem is this: The ABC-* groups are in a different OU than the XYZ-* groups. So for the config shown above, only the ABC groups get mapped, since "Internal" is the OU the ABC groups live in. If I change this: <constructor-arg index="1"><value>OU=Internal</value></constructor-arg> to this: <constructor-arg index="1"><value>OU=Foo</value></constructor-arg> ...then only the XYZ groups get mapped, since "Foo" is the OU the XYZ groups live in. If I change this: <constructor-arg index="1"><value>OU=Internal</value></constructor-arg> to this: <constructor-arg index="1"><value></value></constructor-arg> ...thus, searching the entire base DN, then login fails for all users. (I have cofirmed by using ldapsearch in the CLI that all groups can be searched from the base DN for this environment.) Any clues on why logins all fail when I do this in Jasper? Any thoughts on how to acheive what I am trying to do? Would any further detail or clarification be helpful to answer these questions? Thanks.

I would like to script an automated installation of JRS 5.6, so when I run, ./jasperreports-server-cp-5.6.0-linux-x64-installer.run ... I would like to do so in a non-interactive way, avoiding the prompts for license acceptance and default installation path. Is this possible?

userDnPatterns is not viable because the search needs (and multi-branching of user records) are actually a bit more complex than the example I posted here. Howver, I did implement your 2nd suggestion prior to your posting it, and that seems to work fine. I guess I still wonder why not specifying the branch at all (and simply searching the entire base path) takes such a long time. If I perform an indentical search (of the entire base path) on the CLI using ldapsearch, the result is returned immediately.

I am seeing an LDAP issue in JRS 5.5. LDAP (Active Directory) authentication is configured and working as expected. However, users are in multiple branches, ie: CN=exampleuser1,OU=Users,DC=mycompany,DC=com CN=exampleuser2,OU=Staff,DC=mycompany,DC=com If configured as follows, then only exampleuser1 (and other users in ou=Users) can log in: <bean id="userSearch" class="org.springframework.security.ldap.search.FilterBasedLdapUserSearch"> <constructor-arg index="0"> <value>ou=Users</value> </constructor-arg> <constructor-arg index="1"> <value>(sAMAccountName={0})</value> </constructor-arg> <constructor-arg index="2"> <ref local="ldapContextSource" /> </constructor-arg> <property name="searchSubtree"> <value>true</value> </property> </bean> <bean id="ldapContextSource" class="com.jaspersoft.jasperserver.api.security.externalAuth.ldap.JSLdapContextSource"> <constructor-arg value="ldaps://1.2.3.4:636/dc=mycompany,dc=com"/> <!-- manager user name and password (may not be needed) --> <property name="userDn" value="CN=manager1,OU=staff,dc=mycompany,dc=com"/> <property name="password" value="manager_password"/> <property name="referral" value="follow" /> </bean> If the search branch is changed to Staff, then only exampleuser2 (and other users in ou=Staff) can log in: <constructor-arg index="0"> <value>ou=Staff</value> </constructor-arg> If the search branch is left unspecified, then all users can log in, BUT login takes about 60 seconds: <constructor-arg index="0"> <value></value> </constructor-arg> How can I either (1) specify multiple search branches, or (2) eliminate the long delay when leaving the search branch unspecified?

With a working JRS 5.5 Pro installtion, I am trying to move the Jasperserver Metadata DB to an external postgres host. I have the jasperserver database imported (and running fine) on the external postgres host. I have modified both js.jdbc.properties and classes/js.jdbc.properties (not sure if both need to be modified) as follows: # jasperserver repo db settingsmetadata.jdbc.driverClassName=org.postgresql.Drivermetadata.jdbc.url=jdbc:postgresql://external-postgres-host.mydomain.mytld:5432/jasperservermetadata.jdbc.username=external-postgres-usermetadata.jdbc.password=external-postgres-passwordmetadata.jdbc.password.escapeXML=external-postgres-password However, after restarting JRS, JRS seems to ignore these properities and still connect to the postgres metadata DB on localhost. What's missing here?

I am testing an installation of JRS 5.5, and am using the orgId parameter to specify Organization in the login URL. ie: http://myserver.mydomain.tld/jasperserver-pro/login.html?orgId=organization_1 Upon page load, this seems to work for a moment, in that only the User ID and Password fields are displayed on the login page. However, after about 4 seconds, the Organzation field appears, thus prompting the user for an Organzation, User ID, and Password, even though the orgId has been specified in the URL. Any idea why this might be happening? Thanks.

Thank you, that is helpful. By the way, did you see my side question from above: Where would the appropriate place be to set the default login URL to contain the orgId parameter? ie: /login.html?orgId=organization_1

Where would the appropriate place be to set the default login URL to contain the orgId parameter? ie: /login.html?orgId=organization_1

This does seem to be a workaround, yes. I guess this would prevent any local (non-LDAP) users from being able to change their passwords, right? If so, for that reason, it is probably not a permanent workaround. No matter what, if you could keep me posted on the status on your end, that would be extrememly helpful. Thanks again for your help. It is much appreciated.

Okay, progress... allowUserPasswordChange was actually set to true. This must be the default, since I hadn't previously touched jasperserver-servlet.xml. I tried setting this to false, and the results were the same: Internal Server Error. BUT... I tried again leaving allowUserPasswordChange=false and this time changing passwordExpirationInDays=365 to passwordExpirationInDays=-1, and this time, login succeeded with no Interal Server Error.

Yes, TESTLDAPUSER is created under organization_1. TESTLDAPUSER is all caps in the database, and that is what is being entered in the web login. As a test, I also tried using all lowercase in the web login, and the results were the same. This property is not set, so I trust the default active. Nothing unusual. Full config "applicationcontext-externalauth-ldap-mt.xml" is attached to the original post if you want to take a look. No other custom config beyond what is in that document. In terms of the login procedure itself, nothing unusual at all. Simply entering User ID and Password in the web login and pressing Login. I have tried leaving Organization blank and also filling Organization with "organization_1" with the same results for both cases. Adding this parameter did have the effect of eliminating the Organization field from the web login form, but the error and results were the same after logging in. Please let me know what other info I can provide. Hoping to solve this! Much thanks.

I can now confirm that I have also tested this in 5.5 with the exact same error and log results.

Sounds like you may be experiencing the same issue I posted about yesterday: internal server error on successful ldap login

I have LDAP external authentication (via Active Directory) working in JRS 5.2. Users can successfully log in with their external credentials. However, immediately upon login, the user is initially shown a page that says, "Internal server error occured. Please contact your system administrator." The logged in user can then proceed to click anywhere to which he has been granted access (ie: Library) and from there, JRS functions normally for the logged in user. But obviously, I need to eliminate the error page that appears right after login. Here are the logs that show this happening. I've highlighted what I would guess to be the relevant lines in red: Here is ldapExternalTenantProcessor from applicationContext-externalAuth-LDAP-mt.xml:(Note that I am mapping all logins into a single default organization.) <bean id="ldapExternalTenantProcessor" class="com.jaspersoft.jasperserver.multipleTenancy.security.externalAuth.processors.ldap.LdapExternalTenantProcessor" parent="abstractExternalProcessor"> <property name="ldapContextSource" ref="ldapContextSource"/> <property name="multiTenancyService"><ref bean="internalMultiTenancyService"/></property> <property name="excludeRootDn" value="true"/> <property name="organizationRDNs"><list /></property> <property name="rootOrganizationId" value="organization_1" /> <property name="defaultOrganization" value="organization_1"/> </bean>[/code]The full applicationContext-externalAuth-LDAP-mt.xml is attached below. Any insight into what's going on here? Thanks.