Bug 553636 - dsgw and ds has problems in schema
Summary: dsgw and ds has problems in schema
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: UI - Gateway/Phonebook
Version: 1.1.3
Hardware: i386
OS: Linux
low
high
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 389_1.2.7
TreeView+ depends on / blocked
 
Reported: 2010-01-08 13:56 UTC by Markku Sopula
Modified: 2015-12-07 17:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Centos 5.4 i386
Last Closed: 2015-12-07 17:18:11 UTC


Attachments (Terms of Use)

Description Markku Sopula 2010-01-08 13:56:39 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install from epel
2. setup via setup-ds-admin.pl
3. run setup-ds-dsgw
4. Restart the server
5. Try add new user via dsgw (with admin account)
  
Actual results:
Adding user...
Problem

An error occurred while contacting the LDAP server.
(Object class violation - unknown object class "nsaimpresence" )
The directory server could not honor your request because it violates the schema requirements. Typically, this means that you have not provided a value for a required field. It could also mean that the schema in the directory server needs to be updated.

Expected results:
User added to database

Additional info:
Also graphics in dsgw are not right. worked better with previos versions. Seems that nssaimpresence is removed from schema, but not from dsgw. Older version has nssaimpresence also in ldap schema.

Comment 2 Rich Megginson 2010-10-20 21:13:55 UTC
commit 34a9b5878c33b7ae6c7f888dc2e056f533a887df
Author: Rich Megginson <rmeggins@redhat.com>
Date:   Tue Oct 12 11:06:41 2010 -0600
    the aim schema has been removed from 389 - aim presence is disabled by
    default - disable the aim stuff in dsgw by default - added a new config
    param - have-aim-schema - enable this if you really want to use aim
    schema


Note You need to log in before you can comment on or make changes to this bug.