Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] null dto in class edu.internet2.middleware.grouper.GrouperSession error.

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] null dto in class edu.internet2.middleware.grouper.GrouperSession error.


Chronological Thread 
  • From: "Sanjay Vivek" <>
  • To: <>
  • Subject: RE: [grouper-users] null dto in class edu.internet2.middleware.grouper.GrouperSession error.
  • Date: Tue, 9 Oct 2007 11:30:02 +0100

I've checked my ldap server and unfortunately it hasn't provisioned any data to the ldap server. Perhaps ldappc is not able to locate the Subject entries in the JDBC source? That's the only thing I can think of at the moment.
 
Cheers
Sanjay


From: maliang [mailto:]
Sent: 09 October 2007 10:47
To: Sanjay Vivek
Subject: Re: [grouper-users] null dto in class edu.internet2.middleware.grouper.GrouperSession error.

If the ldappc has provisioned all of data to ldap server, it also will throw this error.

maliang
2007-10-09

发件人: Sanjay Vivek
发送时间: 2007-10-09 17:28:13
收件人:
抄送:
主题: [grouper-users] null dto in class edu.internet2.middleware.grouper.GrouperSession error.
 
Hi everyone,
 
This issue has been raised before but unfortunately I'm stuck at this
point. I'm getting the following error when I run ldappc:
 
FATAL ErrorLog:
[edu.internet2.middleware.ldappc.LdappcGrouperProvisioner] Grouper
Provision Failed: null dto in class
edu.internet2.middleware.grouper.GrouperSession
A FATAL ERROR occurred when running Ldappc.  
Check error log file, correct the problem, and resubmit.
 
I've attached both my sources.xml and ldappc.xml with this email (with
passwords omitted).
 
I believe the main sticking point is the  <source-subject-identifiers >
element in ldappc.xml. Our primary source of NCL subjects is JDBC, and
we would like to configure that as the source from which to present
subjects to Grouper (and ldappc). As shown below, the
<source-subject-identifiers > element identifies for each Subject source
how the provisioner locates the directory entry for a given Subject.
There is a "subjectId" column in our Subjects table in the "jdbc-ncl"
source. However, the  <source-subject-identifiers > element is configured
to locate the Subject's directory entry from a LDAP source and not a
JDBC source. How do I go about configuring  <source-subject-identifiers >
element to locate the Subject's directory entry from a JDBC source
instead? Any insight would be helpful. Cheers.
 
   <source-subject-identifiers >
     <source-subject-identifier source="jdbc_ncl"
subject-attribute="subjectId"  >
       <ldap-search base="ou=people,dc=ncl,dc=ac,dc=uk" 
        scope="subtree_scope" 
        filter="(uid={0})" / >
     </source-subject-identifier >
   </source-subject-identifiers >
 
Regards
--------------
Sanjay Vivek
Web Team
ISS
University of Newcastle Upon Tyne



Archive powered by MHonArc 2.6.16.

Top of Page