Grouper Users - Open Discussion List

[Tom Barton <>]

Some basic questions and requests:

1. What version of grouper are you running?

2. Did you also adjust log4j.logger.edu.internet2.middleware.subject 
                    and 
log4j.logger.edu.internet2.middleware.subject.provider to debug level?

3. What LDAP server & version are you using?

4. Could you send along your sources.xml file (suitably redacted, if 
needs be)?

You might try using gsh to verify & exercise the subject API outside of 
(attempting to) provision groups. What happens if you try something like:

gsh-0.1.0 0% findSubject("someId")

where someId is a value of the ldap attribute you search on in the 
"searchSubject" searchType declaration? Example: if I'm using 
ucPersonRegId as my subject identifier, I'll have 
'(ucpersonregid=%TERM%)' as the essential part of the searchSubject 
searchType declaration. So, if my udPersonRegId is 12345678A, 
findSubject('12345678A') ought to return a little info about me from the 
ldap directory.

Tom


 wrote:
> At 3:55 PM +0000 2/20/07, GW Brown, Information Systems and Computing 
> wrote:
> > Hi Steven,
> >
> > grouper/conf/log4j.properties has:
> >
> > log4j.logger.edu.internet2.middleware.grouper.XmlExporter = INFO, 
> > grouper_event
> > log4j.logger.edu.internet2.middleware.grouper.XmlImporter = INFO, 
> > grouper_event
> >
> > That file also has the locations of log files.
>
> yep -- had already found that file, and changed the log level to DEBUG
>
> my import ran for 60+ minutes (as opposed to the usual 9 seconds...)
>
> it did eventually produce an error log file containing the lines pasted 
> in below.....
>
> I pasted the dns name, etc from a working shibboleth config into my 
> source config.... so I'm pretty sure they're correct....
>
> is there an easy way to "test" (validate) a source definition?
>
> -----------------------------------------------------
>
> 2007-02-20 12:01:02,045: Naming Error Request: 1 cancelled
> javax.naming.CommunicationException: Request: 1 cancelled
>     at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
>
> (many lines removed)
>     at edu.internet2.middleware.grouper.XmlImporter.main(Unknown Source)
> 2007-02-20 12:01:02,045: Naming Error Request: 1 cancelled
> javax.naming.CommunicationException: Request: 1 cancelled
>     at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
>
> (many lines removed)
>
>     at edu.internet2.middleware.grouper.XmlImporter.main(Unknown Source)
> 2007-02-20 12:01:02,057: Unable to init Source: Brown
> edu.internet2.middleware.subject.SourceUnavailableException: Unable to 
> init JNDI source
>     at 
> edu.internet2.middleware.subject.provider.JNDISourceAdapter.init(Unknown 
> Source)
>
> (lines removed)
>
>     at edu.internet2.middleware.grouper.XmlImporter.main(Unknown Source)
> Caused by: edu.internet2.middleware.subject.SourceUnavailableException: 
> Naming Error
>     at 
> edu.internet2.middleware.subject.provider.JNDISourceAdapter.setupEnvironment(Unknown 
> Source)
>     ... 25 more
> Caused by: javax.naming.CommunicationException: Request: 1 cancelled
>     at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
>
> (lines removed)
>
>
>     at 
> javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
>     ... 26 more
> 2007-02-20 12:01:02,057: Unable to init Source: Brown
> edu.internet2.middleware.subject.SourceUnavailableException: Unable to 
> init JNDI source