If you have a commercial version of JasperReports Server, you can choose to map all external users to a single organization; for example, in the following cases:
| • | You have a commercial JasperReports Server deployment that does not implement multiple organizations, but instead uses the default organization. This includes commercial versions that are licensed for a single organization. In this case, externally authenticated users must be mapped to the default organization. |
| • | You have multiple organizations in JasperReports Server, but still want all external users to be placed in a single organization. |
The following steps show how to map all external users to a single organization using the sample-applicationContext-externalAuth-LDAP-mt.xml file:
| 1. | In sample-applicationContext-externalAuth-LDAP-mt.xml, locate the first instance of the ldapExternalTenantProcessor bean and comment the bean out. |
| 2. | Locate the second instance of the ldapExternalTenantProcessor bean and uncomment it. |
| 3. | Set the defaultOrganization property to the organization you want assigned to all external LDAP users. |
| The ldapExternalTenantProcessor bean is not available in the community edition. You do not need to set the organization in the community edition. ldapExternalTenantProcessor is an example of a processor. For more information about processors, see Creating a Custom Processor. |
The following example places all external users in the default organization, organization_1.
<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="defaultOrganization" value="organization_1"/></bean>[/code] |
| Make sure to specify a value for the defaultOrganization. If defaultOrganization is left empty, users may be mapped to the null organization id. This id is usually reserved for special users such as the system administrator and allows access to the repository folder of all other organizations. |
Recommended Comments
There are no comments to display.