Grouper Users - Open Discussion List

["Sanjay Vivek" <>]

Hi Tom, 

I've just checked and made sure all the working grouper config files are
in the ldappc's conf folder and it seems okay to me. I've also turned up
the logging levels to debug and the logging info is given below. As far
as I can tell, everything looks alright to me. Ldappc seems to be
loading up the sources properly and also connects to LDAP. Do you notice
anything out of the ordinary in the logs below? Cheers. 


INFO logging.DebugLog: [edu.internet2.middleware.ldappc.Ldappc] Starting
the Ldappc Program
INFO logging.DebugLog: Running version: 1.0
INFO logging.DebugLog: Created on: 2007-01-11
INFO logging.DebugLog: [edu.internet2.middleware.ldappc.InputOptions]
Starting Ldappc with the following arguments:
INFO logging.DebugLog: [edu.internet2.middleware.ldappc.InputOptions]
-subject
INFO logging.DebugLog: [edu.internet2.middleware.ldappc.InputOptions]
GrouperSystem
INFO logging.DebugLog: [edu.internet2.middleware.ldappc.InputOptions]
-groups
INFO logging.DebugLog:
[edu.internet2.middleware.ldappc.LdappcProvisionControl] ***** Starting
Provisioning *****
DEBUG provider.SourceManager: Instantiating new Digester.
DEBUG provider.SourceManager: Instantiating new Digester.
DEBUG provider.SourceManager: Parsing config input stream:
java.io.BufferedInputStream@182da3d
DEBUG provider.SourceManager: Parsing config input stream:
java.io.BufferedInputStream@182da3d
DEBUG provider.SourceManager: Loading source: g:gsa
DEBUG provider.SourceManager: Loading source: g:gsa
DEBUG provider.BaseSourceAdapter: Loading search: searchSubject
DEBUG provider.BaseSourceAdapter: Loading search: searchSubject
DEBUG provider.BaseSourceAdapter: Loading search:
searchSubjectByIdentifier
DEBUG provider.BaseSourceAdapter: Loading search:
searchSubjectByIdentifier
DEBUG provider.BaseSourceAdapter: Loading search: search
DEBUG provider.BaseSourceAdapter: Loading search: search
DEBUG provider.SourceManager: Loading source: jdbc_ncl
DEBUG provider.SourceManager: Loading source: jdbc_ncl
DEBUG provider.JDBCSourceAdapter: Loading JDBC driver:
com.mysql.jdbc.Driver
DEBUG provider.JDBCSourceAdapter: Loading JDBC driver:
com.mysql.jdbc.Driver
INFO provider.JDBCSourceAdapter: JDBC driver loaded.
INFO provider.JDBCSourceAdapter: JDBC driver loaded.
DEBUG provider.JDBCSourceAdapter: Initializing connection factory.
DEBUG provider.JDBCSourceAdapter: Initializing connection factory.
DEBUG provider.JDBCSourceAdapter: Connection factory initialized.
DEBUG provider.JDBCSourceAdapter: Connection factory initialized.
INFO provider.JDBCSourceAdapter: Data Source initialized.
INFO provider.JDBCSourceAdapter: Data Source initialized.
DEBUG provider.BaseSourceAdapter: Loading search: searchSubject
DEBUG provider.BaseSourceAdapter: Loading search: searchSubject
DEBUG provider.BaseSourceAdapter: Loading search:
searchSubjectByIdentifier
DEBUG provider.BaseSourceAdapter: Loading search:
searchSubjectByIdentifier
DEBUG provider.BaseSourceAdapter: Loading search: search
DEBUG provider.BaseSourceAdapter: Loading search: search
DEBUG provider.SourceManager: Loading source: ldap_ncl
DEBUG provider.SourceManager: Loading source: ldap_ncl
DEBUG provider.JNDISourceAdapter: Creating Directory Context
DEBUG provider.JNDISourceAdapter: Creating Directory Context
INFO provider.JNDISourceAdapter: Success in connecting to LDAP
INFO provider.JNDISourceAdapter: Success in connecting to LDAP
DEBUG provider.SourceManager: Loading source: g:isa
DEBUG provider.SourceManager: Loading source: g:isa
DEBUG provider.JNDISourceAdapter: searchType: searchSubject filter: (&
(eduPersonPrincipalName=GrouperSystem) (objectclass=eduPerson)) base:
ou=people,dc=ncl,dc=ac,dc=uk scope: SUBTREE_SCOPE
DEBUG provider.JNDISourceAdapter: searchType: searchSubject filter: (&
(eduPersonPrincipalName=GrouperSystem) (objectclass=eduPerson)) base:
ou=people,dc=ncl,dc=ac,dc=uk scope: SUBTREE_SCOPE
DEBUG logging.DebugLog:
[edu.internet2.middleware.ldappc.GrouperSubjectRetriever] Found
GrouperSystem
INFO grouper.EventLog:
[957c927b-c906-433c-96ad-4bcea3c5f824,'GrouperSystem','application']
session: start (25ms)
INFO logging.DebugLog: Started GrouperSession:
957c927b-c906-433c-96ad-4bcea3c5f824,'GrouperSystem','application'
INFO grouper.EventLog:
[957c927b-c906-433c-96ad-4bcea3c5f824,'GrouperSystem','application']
session: stop duration=64ms (4ms)
INFO logging.DebugLog: [edu.internet2.middleware.ldappc.Ldappc] End of
Ldappc execution.


>-----Original Message-----
>From: Tom Barton 
>[mailto:]
> 
>Sent: 10 October 2007 22:14
>To: Sanjay Vivek
>Cc: Grouper Users
>Subject: Re: [grouper-users] null dto in class 
>edu.internet2.middleware.grouper.GrouperSession error.
>
>Your subordinate-stem-queries element looks right to me. A 
>sanity check: 
>do you have working grouper config files in ldappc's conf 
>folder (ehcache.xml, grouper.hibernate.properties, and 
>grouper.properties)? If you do, perhaps the next step is to 
>look at appropriate debug logging. 
>You probably have a statement like the following in your 
>log4j.properties file:
>
>log4j.logger.edu.internet2.middleware.ldappc.logging.DebugLog 
>   = INFO, ldappc_debug
>
>In addition to replacing 'INFO' with 'debug', please add
>
>log4j.logger.edu.internet2.middleware.grouper.EventLog = info, 
>ldappc_debug log4j.logger.edu.internet2.middleware.subject = 
>info, ldappc_debug 
>log4j.logger.edu.internet2.middleware.subject.provider = info, 
>ldappc_debug
>
>and see if further clues to the problem emerge.
>
>Sanjay Vivek wrote:
>> Hi everyone,
>> 
>> Unfortunately, I'm still unable to provision my groups in Grouper to 
>> the LDAP server. I'd describe briefly the Grouper scenario I 
>have in place.
>> As a test run, I have a root stem (ncl), and a stem underneath 
>> (ncl:services). I also have 4 groups within ncl:services. 
>There are 2 
>> users in each group. I basically want to provision 
>everything under my 
>> root stem to LDAP. The <subordinate-stem-queries> element in 
>> ldappc.xml is stated below:
>> 
>> <subordinate-stem-queries>
>>         <stem-list>
>>          <stem>ncl</stem>
>>         </stem-list>
>> </subordinate-stem-queries>
>> 
>> Have I got this right? Are there any other config files besides 
>> ldappc.xml and sources.xml that I have to edit to get it work? I 
>> believe I have the ldappc working in principle but it's not 
>> provisioning the grouper data to LDAP. Any help would be 
>greatly appreciated. Cheers.
>> 
>> Regards
>> Sanjay
>> 
>>> -----Original Message-----
>>> From: Tom Barton 
>>> [mailto:]
>>> Sent: 09 October 2007 15:19
>>> To: Sanjay Vivek
>>> Cc: 
>>> 
>>> Subject: Re: [grouper-users] null dto in class 
>>> edu.internet2.middleware.grouper.GrouperSession error.
>>>
>>> The jdbc_ncl source config declares, in part,
>>>
>>> select
>>>    subject.subjectid as id, subject.name as name,
>>>    lfnamet.lfname as lfname, loginidt.loginid as loginid,
>>>    desct.description as description
>>>
>>> So the name of the attribute attached to a Subject object is 'id' 
>>> rather than 'subjectId'. Hence,
>>>
>>> <source-subject-name-map source="jdbc_ncl"
>>>   subject-attribute="subjectId" />
>>>
>>> should be
>>>
>>> <source-subject-name-map source="jdbc_ncl"
>>>   subject-attribute="id" />
>>>
>>> And although a corresponding change might be made to the 
>>> <source-subject-identifiers> element, a look over your config files 
>>> makes me wonder if it should instead be
>>>
>>>   <source-subject-identifiers>
>>>     <source-subject-identifier source="jdbc_ncl"
>>>         subject-attribute="loginid" >
>>>       <ldap-search base="ou=people,dc=ncl,dc=ac,dc=uk"
>>>         scope="subtree_scope"
>>>         filter="(uid={0})" />
>>>     </source-subject-identifier>
>>>   </source-subject-identifiers>
>>>
>>> Ie, is the 'loginid' attribute in your jdbc source the same as the 
>>> 'uid'
>>> attribute for the corresponding Subject in LDAP? If so, that's how 
>>> you want to tell Ldappc to identify jdbc-presented Subjects with 
>>> their LDAP-presented counterparts. But if your subjectId is really 
>>> the uid value, then make subject-attribute="id".
>>>
>>> You might still get a "null dto" error even if the provisioning 
>>> worked correctly - that bug has been noted.
>>>
>>> Hope this helps,
>>> Tom
>>>
>>> Sanjay Vivek wrote:
>>>> 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
>