Previous Page Next Page
Configuring the LDAP Server
Configuring via UI
Configuring with LDAPProperties.xml
Troubleshooting LDAP server configuration
To use an LDAP server's security system, you should first enable JReport Server to adapt to a directory server. You can configure either via UI or with the LDAPProperties.xml file.
Currently the following directory servers are supported: Novell Directory Server, Microsoft Site Server, iPlanet Directory Server, Active Directory Advanced Server, Lotus Domino Server and OpenLDAP Directory Server. If you need access to a different directory server, contact your JReport Sales Representative. New servers are frequently being added.
Configuring via UI
To configure the LDAP server via UI, on the JReport Administration Page, go to the Configuration > LDAP > Server tab, then specify the following options as required.
Option |
Description |
Select LDAP Server |
Specifies the directory server. Supported servers are: Novell Directory Server, iPlanet Directory Server, Microsoft Site Server, OpenLDAP Directory Server, Win2000 Active Directory, and Lotus Domino on NT. |
Load Settings |
Loads the settings of the specified LDAP server. |
Enable LDAP Version2/Version3 |
Specifies whether or not to enable JReport Server to retrieve users from the directory server and which LDAP Version to adopt.
The LDAP Version3 extends LDAP Version2 in the areas of internationalization, authentication, referral, and deployment. It also allows new features to be added to the protocol without also requiring changes to the protocol. This is done by using extensions and controls.
LDAP Version3 protocol has extensible authentication which uses Simple Authentication and Security Layer ( SASL) mechanisms so as to support pluggable authentication.
Note that currently when you select Version3, JReport Server will only use LDAP Version3 protocol to connect to LDAP server. |
Enable Direct Authentication to LDAP Server |
Specifies whether or not to enable LDAP without importing LDAP security information. This option controls the LDAP feature's work mode. Currently, the JReport Server security system can run two modes in which you can use an LDAP server's security system. The first is importing mode. In this mode, if you want to use the LDAP feature, you will have to import the security information from an LDAP server. The second is non-importing mode. With this mode, JReport Server can directly access an LDAP server and obtain LDAP security information without having to import it. |
Enable Auto-Import of Users from LDAP Server |
Specifies to enable JReport Server to import LDAP users automatically. If activated, the server security system will import security information from the LDAP server when an LDAP user logs into JReport Server for the first time. |
LDAP URL |
Specifies the URL of the LDAP server. |
LDAP Server Port |
Specifies the port of the LDAP server. |
Root Entry |
Specifies the root of the directory server. From this root, JReport Server searches for objects in directory server. |
Directory Manager DN |
Specifies the entry path of the Directory Manager who has the priority to manage users on the directory server. |
Password |
Specifies the Directory Manager's password. |
Remember Password |
Specifies to remember the Directory Manager's password. |
Encryption Type |
Specifies the encryption type. There are two types available. None means using a plain port to connect to the LDAP server, and SSL refers to connecting to the LDAP server by SSL. |
Import LDAP Groups to |
Specifies whether the users in the LDAP groups will be imported into the JReport security system as local roles or as local groups. |
Test Connection |
Tests whether the connection to the specified server is successful or not. |
User Schema |
Specifies the settings of user schema.
- User Attribute Name
Specifies the user's attribute name.
- User Common Name
Specifies the user's common name.
- User Password
Specifies the user's password.
- Distinguished Name
Specifies the name of the organization unit inside the LDAP server where you want to perform a search for users.
- Query User
Views properties of users in the organization unit.
- Filter
Specifies the filter criteria with which to search for users.
- Specify the attribute for user description
Specifes the specific attribute which will be used as JReport user information.
- Attribute Name
Specifes the attribute name.
|
Group Schema |
Specifies the group schema settings.
- Group Common Name
Specifies a common name for the group.
- Group Member Type
Specifies the member type of the group.
- Distinguished Name
Specifies the name of the organization unit inside the LDAP server where you want to perform a search for groups.
- Filter
Specifies the filter criteria with which to search for groups.
- Admin Group
JReport Server will add the group specified here as a member to the Admin group.
- Query Group
Views properties of groups in the organization unit.
- Specify the attribute for group description
Specifes the specific attribute which will be used as JReport group information.
- Attribute Name
Specifes the attribute name.
|
The following presents examples for adapting JReport Server to specific directory servers:
Example 1: Configuration for adapting to a Novell Directory Server
- Select Novell Directory Server from the Select LDAP Server drop-down list, and then click Load Settings. The settings of the Novell Directory Server will then be loaded.
- Check the Enable LDAP checkbox, and input the following information:
- LDAP URL: ldap://IP address or host name of your Novell Directory Server (for example:
ldap://127.0.0.1
)
- LDAP Server Port: 389
- Root Entry: o=the name of the root (for example: o=myorg)
- Directory Manager DN: cn=user name of the directory manager,o=context (for example: cn=admin,o=context)
- Password: the password of the Directory Manager (for example: 1234)
- Encryption Type: None
- Import LDAP Groups to: Group
- User Schema
- Distinguished Name: ou=the name of the organization unit where you want to perform a search for users (for example: ou=orgunit)
- Filter: (&(cn=the filter criteria that you want to set )(objectclass=person)) (for example: (&(cn=*)(objectclass=person)))
- Group Schema
- Distinguished Name: ou=the name of the organization unit that you want to perform a search for groups (for example: ou=orgunit)
- Filter: (&(cn=the filter criteria that you want to set )(objectclass=groupofuniquenames)) (for example: (&(cn=*)(objectclass=groupofuniquenames)))
- Admin Group: The name of the group you want to add to the Admin group (for example: develop)

- You can test the connection settings by clicking the Test Connection button, get the query result of the users specified in the option Filter by clicking the Query User button, and get the query result of groups specified in the option Filter by clicking the Query Group button.
- Click Save to save all settings. You can then get all users and groups from the orgunit organizational unit.
Example 2: Configuration for adapting to a Microsoft Site Server
- Select Microsoft Site Server from the Select LDAP Server drop-down list, and then click Load Settings. The settings of the Microsoft Site Server will be loaded.
- Make sure that the Enable LDAP checkbox is selected, and input the following information:
- LDAP URL: ldap://IP address or host name of your Microsoft site Server (for example:
ldap://127.0.0.1
)
- LDAP Server Port: 1003
- Root Entry: o=test
- Directory Manager DN: cn=administrator,ou=members,o=test
- Password: test
- Encryption Type: None
- Import LDAP Groups to: Group

- Click Save to save all settings in this page.
You can then get all users from the members organizational unit and all groups from the groups organizational unit.
Example 3: Configuration for adapting to an iPlanet Directory Server
- Select iPlanet Directory Server from the Select LDAP Server drop-down list, and then click Load Settings. The settings of iPlanet Directory Server will then be loaded.
- Make sure that the Enable LDAP checkbox is selected, and input the following information:
- LDAP URL: ldap://IP address of your iPlanet Directory Server
- LDAP Server Port: 389
- Root Entry: dc=mailbj,dc=jinfonet,dc=com
- Directory Manager DN: cn=directory manager
- Password: jinfonet
- Encryption Type: None
- Import LDAP Groups to: Group

- Click Save to save all the settings in this page. You can then get all users in the people organizational unit and all groups in the groups organizational unit.
Example 4: Configuration for adapting to the Active Directory Advanced Server
- Select Win2000 Active Directory from the Select LDAP Server drop-down list, and then click Load Settings. The settings are then cleared and you can input your information.
- Make sure that the Enable LDAP checkbox is selected, and input the following information:
- LDAP URL: ldap://IP address of your Windows 2000 Advanced Server
- LDAP Server Port: 389
- Root Entry: DC=testad,DC=local
- Directory Manager DN: CN=administrator,CN=Users,DC=testad,DC=local
- Password: 1234
- Encryption Type: None
- Import LDAP Groups to: Group
- User Schema
- User Attribute Name: cn
- User Common Name: userPrincipalName
- User Password: userPassword
- Distinguished Name: ou=myorg
- Filter: (&(cn=*)(objectclass=person))
- Group Schema
- Group Common Name: cn
- Group Member Type: member
- Distinguished Name: ou=myorg
- Filter: (&(cn=*)(objectclass=group))


- Click Save to save all settings in this page. You can then get all users and groups from the myorg organizational unit.
Example 5: Configuration for adapting to a Lotus Domino Server on NT
- Select Lotus Domino on NT from the Select LDAP Server drop-down list, and then click Load Settings. The settings are then cleared and you can input your information.
- Make sure that the Enable LDAP checkbox is selected, and input the following information:
- LDAP URL: ldap://IP address of your Lotus Domino Server
- LDAP Server Port: 389
- Root Entry:
- Directory Manager DN: cn=admin,o=jtotal
- Password: 123456
- Encryption Type: None
- Import LDAP Groups to: Group
- User Schema
- User Attribute Name: uid
- User Common Name: cn
- User Password: userPassword
- Distinguished Name: ou=developer, o=jtotal
- Filter: (&(cn=*)(objectclass=person))
- Group Schema
- Group Common Name: cn
- Group Member Type: member
- Distinguished Name:
- Filter: (&(cn=*)(objectclass=groupofnames))


- Click Save to save all settings in this page. You can then get all users and groups from the developer organization unit.
Example 6: Configuration for adapting to an OpenLDAP Directory Server
- Select OpenLDAP Directory Server from the Select LDAP Server drop-down list, and then click Load Settings. The settings are then cleared and you can input your information.
- Make sure that the Enable LDAP checkbox is selected, and input the following information:
- LDAP URL: ldap://IP address of your OpenLDAP Directory Server (for example:
ldap://127.0.0.1
)
- LDAP Server Port: 389
- Root Entry: dc=openldap, dc=ldaptest
- Directory Manager DN: cn=Manager,dc=openldap,dc=ldaptest
- Password: 123456789
- Encryption Type: None
- Import LDAP Groups to: Group
- User Schema
- User Attribute Name: uid
- User Common Name: cn
- User Password: userPassword
- Distinguished Name: ou=members
- Filter: (&(uid=*)(objectclass=person))
- Group Schema
- Group Common Name: cn
- Group Member Type: uniqueMember
- Distinguished Name: ou=groups
- Filter: (&(cn=*)(objectclass=groupofuniquenames))
- Admin Group:


- Click Save to save all settings in this page. You can then get all users and groups from the developer organization unit.
Notes:
- Make sure that the Directory Manager DN is a user with prior LDAP Server permission, and who can retrieve other LDAP users.
- Make sure that the users and groups you want to query and import into JReport Server belong to the organization you typed into the Distinguished Name field.
Configuring with LDAPProperties.xml
The file LDAPProperties.xml located in <install_root>\properties
can be used for LDAP server configuration. The properties in the file can be mapped to the options in the Server tab on the JReport Administration > Configuration > LDAP page. For details about the usages of the properties, refer to that of the mapped options.
UI Option |
Properties in LDAPProperties.xml |
Enable LDAP |
enableLDAPSupport |
Version2/Version3 |
ldapVersion |
Enable Direct Authentication to LDAP Server |
enableNoneImportedLDAPSupport |
Enable Auto-Import of Users from LDAP Server |
enableAutoImportLDAPUser |
LDAP URL |
url |
LDAP Server Port |
serverPort |
Root Entry |
rootEntry |
Directory Manager DN |
directoryManagerDN |
Password |
password |
Encryption Type |
isUsingSSL |
Import LDAP Groups to |
importGroupType |
User Attribute Name |
userAN |
User Common Name |
userCN |
User Password |
userPassword |
Distinguished Name |
userDN |
Filter (for user schema) |
userFilter |
Specify the attribute for user description |
userEnableSAN |
Attribute Name (for user schema) |
userSAN |
Group Common Name |
groupCN |
Group Member Type |
groupMemeberType |
Distinguished Name |
groupDN |
Filter (for group schema) |
groupFilter |
Admin Group |
groupAdminGroup |
Specify the attribute for group description |
groupEnableSAN |
Attribute Name (for group schema) |
groupSAN |
Troubleshooting LDAP server configuration
When you encountered any problems during the LDAP configuration, refer to the following for help.
LDAP configuration failure resulting in re-login failure as an admin user
An admin user may fail to carry out LDAP configuration properly, and thus then cannot log onto the JReport Administration page to manage the server. If this happens, you should follow the below steps:
- Modify the property in the LDAP configuration XML file LDAPProperties.xml in
<install_root>\properties
as follows to turn off the Enable Direct Authentication to LDAP Server option:
<env-enableNoneImportedLDAPSupport>false</env-enableNoneImportedLDAPSupport>
- Restart JReport Server and log in as a built-in security admin user to correct the LDAP configuration.
Warning messages in the advent of incorrect LDAP configuration
Apart from the notes offered on the JReport Administration > Configuration > LDAP page, prompt warning information is also provided in order to cope with incorrect LDAP configuration. The server system will prompt warning messages in the following cases:
- If you do not fill in the Admin Group field or specify an admin group.
- If the admin group specified does not hold a user.
- If the admin group specified does not exist in the LDAP server.
Previous Page Next Page