Novell Documentation: eDirectory with FreeRADIUS - Solutions for Commonly Faced Problems

Solutions for Commonly Faced Problems

This section lists some scenarios for extending the eDirectory schema.

Scenario 1: If the object class by FreeRADIUS radiusprofile is already existing in eDirectory.
Solution: You need not extend the schema.
Scenario 2: If the object class by FreeRADIUS radiusprofile is visible in iManager.
Solution: You can edit it through iManager.
Scenario 3: If the object class by FreeRADIUS radiusprofile is not visible in iManager.
- Scenario 1: If schema mapping is absent.
  Solution: You need to map the schema through iManager.
- Scenario 2: If schema mapping is present but not visible.
  Solution: You need to extend the schema by using LDIF files. Refer Extending the eDirectory Schema Using LDIF Files for more information.

Extending the eDirectory Schema Using LDIF Files

You can extend the eDirectory schema using ldif files, in case you are not able to extend through the iManager plug-in. The iManager plug-in package contains the following ldif files which can be used to extend the schema:

addclassmap.ldif
RADIUS-LDAPv3.ldif

The addclassmap.ldif file is used to change the mapping, as eDirectory already has the rADIUSProfile object class which is a part of the Novell RADIUS server. The objectclass required by FreeRADIUS is also called radiusprofile and hence the schema extension will not fail unless the mapping is changed.

The RADIUS-LDAPv3.ldif is the LDAPv3 schema for FreeRADIUS.