Difference between revisions of "Documentation/Administration Guide/LDAP Access"
Line 3: | Line 3: | ||
|ShowPrevNext=block | |ShowPrevNext=block | ||
|ShowPrevPage=block | |ShowPrevPage=block | ||
− | |||
|PrevPage=Documentation/Administration Guide/Restricting functionality | |PrevPage=Documentation/Administration Guide/Restricting functionality | ||
− | |||
}} | }} | ||
{{Documentation/Abstract|This chapter describes how {{OOo}} can access user profile settings on an LDAP server.}} | {{Documentation/Abstract|This chapter describes how {{OOo}} can access user profile settings on an LDAP server.}} |
Revision as of 12:51, 17 April 2008
- Apache OpenOffice Basic Macros and Libraries
- Apache OpenOffice Extension Manager
- Adding Template Files to an Apache OpenOffice Installation
- Adding AutoText Files to an Apache OpenOffice Network Installation
- Deactivating the Apache OpenOffice Registration Wizard
- Accessing Email Clients
- Customizing the User Interface
- Restricting Functionality in Apache OpenOffice
- Accessing Apache OpenOffice User Profiles on an LDAP Server
< {{#switch:Previous Page | Previous Section = Previous Section | Next Section = Next Section | Previous Page = Previous Page | Next Page = Next Page | }} | [[{{{NextPage}}}|{{#switch:Next Page | Previous Section = Previous Section | Next Section = Next Section | Previous Page = Previous Page | Next Page = Next Page |
}} >]] |
Manually Configuring Apache OpenOffice to Access User Profiles on an LDAP Server
Apache OpenOffice 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 Apache OpenOffice on a network.
To retrieve user profiles for Apache OpenOffice 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 Apache OpenOffice user profile
Configuring Apache OpenOffice 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 Apache OpenOffice can retrieve user profiles from an LDAP repository. Apache OpenOffice 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 Apache OpenOffice to Access User Profiles From an LDAP Repository
- In a text editor, create an XML configuration file with the name LDAP.xcu
Template:Documentation/Note
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.
- SearchPassword
- Password of SearchUser.
- 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.
- Replace the value placeholders in the LDAP.xcu file with the mandatory settings for your LDAP server.
- Copy the LDAP.xcu file to <Apache OpenOffice installation>/share/registry/data/org/openoffice/
Mapping LDAP User Profiles
By default, a Apache OpenOffice installation includes two meta-configuration mapping files that map Apache OpenOffice user profile attributes to LDAP attributes. The LDAP User Profile Back End uses the <Apache OpenOffice installation>/share/registry/ldap/oo-ldap-attr.map mapping file for a Sun Java System Directory Server and the <Apache OpenOffice 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.
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
- In a text editor, create a text file with the name oo-ldap server type-attr.mapTemplate:Documentation/Tip
- 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>Template:Documentation/Note - Copy the mapping file to the <Apache OpenOffice installation>/share/registry/ldap/ directory.Template:Documentation/Note
- In a text editor, open the <Apache OpenOffice installation>/share/registry/data/org/openoffice/LDAP.xcu file.
- 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). |