Accessing OpenOffice.org User Profiles on an LDAP Server

From OpenOffice.org Wiki

Jump to: navigation, search
PAGE_TITLE: QWNjZXNzaW5nIE9wZW5PZmZpY2Uub3JnIFVzZXIgUHJvZmlsZXMgb24gYW4gTERBUCBTZXJ2ZXI=
doc OOo
< Previous Page [[{{{NextPage}}}|Next Page >]]

OpenOffice.org can use an LDAP User Profile Back End to access user profiles, such as first name, last name, and address, on an LDAP server. As a result, you do not need to manually enter user profiles when you install OpenOffice.org on a network.

To retrieve user profiles for OpenOffice.org from an LDAP repository, you need to provide the LDAP User Profile Back End with the following information:

  • Location of the LDAP repository
  • Mapping file that identifies the attributes in the LDAP repository which are required to generate a OpenOffice.org user profile

Configuring OpenOffice.org to Retrieve User Profiles From an LDAP Repository

You can specify the settings for the LDAP User Profile Back End in LDAP.xcu, an XML file, so that OpenOffice.org can retrieve user profiles from an LDAP repository. OpenOffice.org loads these settings during startup. The structure of the LDAP.xcu file is defined by the configuration schema for the org.openoffice.LDAP component. The schema is located in <install>/share/registry/schema/org/openoffice/LDAP.xcs.

To Configure OpenOffice.org to Access User Profiles From an LDAP Repository

  1. In a text editor, create an XML configuration file with the name LDAP.xcu
    Image:documentation_note.pngYou can find a sample LDAP.xcu at <OpenOffice.org installation>/share/registry/data/org/openoffice/LDAP.xcu.sample

    The following is the structure of the LDAP.xcu.sample file: 

    <oor:component-data oor:name="LDAP" oor:package="org.openoffice" 
 xmlns:oor="http://openoffice.org/2001/registry" 
 xmlns:xs="http://www.w3.org/2001/XMLSchema" 
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <node oor:name="UserDirectory">
   <node oor:name="ServerDefinition">
     <prop oor:name="Server" oor:type="xs:string">
       <value>ldapserver.mycorp.com</value>
     </prop>
     <prop oor:name="BaseDN" oor:type="xs:string">
       <value>dc=mycorp,dc=com</value>
     </prop>
     <prop oor:name="Port" oor:type="xs:int">
       <value>389</value>
     </prop>
   </node>
   <!-- The following settings should be omitted if anonymous access is possible -->
     <prop oor:name="SearchUser" oor:type="xs:string"> 
        <value>MyUserLogin</value>
     </prop> 
     <prop oor:name="SearchPassword" oor:type="xs:string"> 
        <value>MyPassword</value> 
     </prop> 
   <!-- End of strings that should be omitted if anonymous access is possible -->
   <prop oor:name="UserObjectClass" oor:type="xs:string">
     <value>inetorgperson</value>
   </prop>
   <prop oor:name="UserUniqueAttribute" oor:type="xs:string">
     <value>uid</value>
   </prop>
   <prop oor:name="Mapping" oor:type="xs:string">
     <value>oo-ldap</value>
   </prop>
 </node>
 </oor:component-data>
    Server
    Host name of the LDAP Server.
    BaseDN
    Root entry of the enterprise directory.
    Port
    Port number of the LDAP Server. The default port number is 389.
    SearchUser
    Distinguished Name (DN) of an existing user with read-only access to the LDAP repository.
    Image:documentation_note.pngThis setting is only required if anonymous access is not supported by the LDAP server.
    SearchPassword
    Password of SearchUser.
    Image:documentation_note.pngThis setting is only required if anonymous access is not supported by the LDAP server.
    UserObjectClass
    Object class that identifies user entities.
    For example, the user entity for an OpenDS Server inetOrgPerson. To find the DN of a user, you need to use this entity in conjunction with the UserUniqueAttribute attribute.
    UserUniqueAttribute
    Attribute that identifies user entities.
    For example, the UserUniqueAttribute for an LDAP repository that is on an OpenDS server is uid. To find the DN of a user, you need to use this attribute in conjunction with the UserObjectClass. The server compares the value of this attribute to the login user name for the operating system.
    Mapping
    String that indicates a named mapping file, that is, $(Mapping)-attr.map.
    For example, if the LDAP repository is an OpenDS server, the mapping entry is oo-ldap. This entry tells the LDAP User Profile Back End to use oo-ldap-attr.map as the mapping file. Alternatively, if the LDAP repository is an Active Directory, the Mapping entry is oo-ad-ldap. This entry tells the LDAP User Profile Back End to use oo-ad-ldap-attr.map as the mapping file.
  2. Replace the value placeholders in the LDAP.xcu file with the mandatory settings for your LDAP server.
  3. Copy the LDAP.xcu file to <OpenOffice.org installation>/share/registry/data/org/openoffice/

Mapping LDAP User Profiles

By default, a OpenOffice.org installation includes two meta-configuration mapping files that map OpenOffice.org user profile attributes to LDAP attributes. The LDAP User Profile Back End uses the <OpenOffice.org installation>/share/registry/ldap/oo-ldap-attr.map mapping file for a Sun Java System Directory Server and the <OpenOffice.org installation>/share/registry/ldap/oo-ad-ldap-attr.map mapping file for a Windows Active Directory Server. The Mapping entry in the LDAP.xcu file indicates which mapping file to use, for example, oo-ldap indicates the oo-ldap-attr.map file.

Image:documentation_note.pngIf you want to change the location of the mapping files, edit the CFG_LdapMappingUrl entry in the <OpenOffice.org installation>/program/configmgrrc file to point to the new location of the file. In Windows, this entry is in the <OpenOffice.org installation>/program/configmgr.ini file.

If you want, you can also create a custom user profile mapping file for an alternative LDAP server.

To Create a Custom User Profile Mapping File

  1. In a text editor, create a text file with the name oo-ldap server type-attr.map
    Image:Tip.pngEdit a copy of an existing mapping file, for example, <OpenOffice.org installation>/share/registry/ldap/oo-ldap-attr.map.
  2. Enter the mapping information.
    Each line in the file must have the following format:
    <User Profile Attribute>=<LDAP Attribute 1>,<LDAP Attribute 2>,...,<LDAP Attribute N>
    Image:documentation_note.pngYou can only map user profile attributes that are present in the OpenOffice.org configuration schema. The file name path for this schema is <OpenOffice.org installation>/share/registry/schema/org/openoffice/UserProfile.xcs. You can edit the list of corresponding LDAP attributes to show which attributes in the user entries hold the personal data. The LDAP server queries the LDAP attributes in the order that the attributes appear in the list.
  3. Copy the mapping file to the <OpenOffice.org installation>/share/registry/ldap/ directory.
    Image:documentation_note.pngYou need administrator rights to copy the mapping file to this directory on a network installation.
  4. In a text editor, open the <OpenOffice.org installation>/share/registry/data/org/openoffice/LDAP.xcu file.
  5. Change the value of the Mapping property to the string that appears before the -attr.map in the name of the mapping file.
    For example, the value of the Mapping property for the file
Content on this page is licensed under the Public Documentation License (PDL).
Retrieved from "http://wiki.services.openoffice.org/wiki/Documentation/Administration_Guide/LDAP_Access"
Personal tools