Grouper Users - Open Discussion List

[Baron Fujimoto <>]

Sorry, closer examination of the grouper_error.log revealed the problem:
hostname didn't match the hostname in the ldap server's SSL certificate.
Mea culpa :(

It seems that the same configuration for the 2.0.0 instance does not throw
the java.security.cert.CertificateException though.

-baron
-- 
Baron Fujimoto 
<>
 :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum

On Wed, Aug 08, 2012 at 03:48:46AM +0000, Chris Hyzer wrote:
: Can you start GSH, and do a subject search, and send the entire log along 
(or just to me if you like).  Also send a sanitized version of your 
sources.xml.  The ldap source should now use vt-ldap so it is a little 
different, but it should work :)
: 
: Thanks,
: Chris
: ________________________________________
: From: Baron Fujimoto 
[]
: Sent: Tuesday, August 07, 2012 8:41 PM
: To: 

: Subject: [grouper-users] LDAP source unavailable
: 
: I've been trying to upgrade from 2.0.0 to 2.1.1, but am encountering the
: following error when I invoke gsh:
: 
: [main] ERROR SubjectCheckConfig.checkConfig(117) -  - error with subject 
source id: test LDAP, name: LDAP test, problem with getSubject by id, in 
sources.xml: search searchSubject:
: edu.internet2.middleware.subject.SourceUnavailableException: Ldap 
Exception: Pool is empty and object creation failed
: 
: As far as I tell, all of the LDAP credential related items are the
: same in both sources.xml.  Our LDAP logs show the LDAP bind for 2.0.0,
: but nothing for 2.1.1.
: 
: There are other differences between the source.xml files, but it appears
: that the only ones not in id=gsa and id=grouperEntities where you are 
advised,
: "It is recommended that you **not** change the default values for this 
source
: adapter" appear to be related to limiting the number of results per page and
: for inclause related stuff.
: 
: Any ideas?