Grouper Users - Open Discussion List

[Sebastien Gagne <>]

It's hard without configuration sample, but my guess would that it tries to build a stem definition for your root folder and that fails. The problem would be that "ou=Groups,dc=rice,dc=edu" is not part of the bulkSync, this is probably an inconsistency in the configuration where you maybe don't provision your root stem or maybe you do and don't

How do you provision your groups in your LDAP ? flat or bushy ? do you include your root stem ?

---
Sébastien Gagné, M.Ing., ing. jr
Analyste en informatique - Université de Montréal

On Mon, Mar 11, 2013 at 10:49 AM, Paul Engle <> wrote:

All,
  I'm trying to migrate from 1.6.3 to 2.1.3, switching from ldappc (not
even -ng) to psp in the process. Since the configuration is much more
complex, I'm trying to use a pretty stock configuration based on the
psp-example-grouper-to-openldap files provided.

Essentially, the only changes I've made are:
 * site specific configuration in ldap.properties & sources.xml
 * add 'riceGroup' as a group objectClass in the static resolver
 * add a 'givenName' attribute for groups, using the group name attribute


I can sync individual people or groups and everything comes out as
expected. However, when I try a bulkSync, I get the following error:

<psp:bulkSyncResponse xmlns:psp='http://grouper.internet2.edu/psp'
status='failure' requestID='2013/03/11-09:12:47.441' error='customError'>
  <errorMessage>Unable to determine schema entity for
ou=Groups,dc=rice,dc=edu</errorMessage>
</psp:bulkSyncResponse>


That is the groupsBaseDn from ldap.properties, so I'm not sure why it's
trying to get a schema for it. Any hints as to what I can look at are
welcome.

  -paul

--
Paul D. Engle              |  Rice University
Sr. Systems Administrator  |  Information Technology - MS119
(713)348-4702              |  PO Box 1892
           |  Houston, TX 77252-1892