Grouper Developers Forum

[Chris Hyzer <>]

btw, this is the issue CMU had where it was deleted and adding all members with each loader job, this issue is resolved.

I think we should discuss this issue at the next dev call...

In the subject API things should be fine, and in the loader you can fix it easily the way CMU did with the function that massages the ID's (tolowercase?)

The only part that is missing I think is the part of Grouper which finds a Member by subject ID, which could be a case insensitive matching.  This might address the loader issue too.  Maybe this could be an option for Grouper...

Thanks,

Chris

---

From: Michael R. Gettes []
Sent: Wednesday, August 08, 2012 5:22 PM
To: Rahul Doshi
Cc: Chris Hyzer
Subject: Re: [grouper-users] Grouper ldap loader

I'll add to this that while we fixed the problem in this sense - I am not sure to what degree there is a larger problem of properly handling DNs as case insensitive values.  There are lots of LDAP environments where the values in the DNs are case different from values in the LDAP entry.  This may be seen as a robustness question for grouper.

/mrg

On Aug 8, 2012, at 17:07, Rahul Doshi wrote:

Hi Chris,

I was able to find the problem.  It turns out that member attribute stored in our LDAP environment is in uppercase where as subjectId stored in database is lowercase.  So when the calculating the deltas match on what is stored in database and what is in LDAP fails, which is causing everything to be deleted and added back.  I was able to fix the problem by simply forcing return value to be lowercase in my CmuLoaderElUtils.convertDnToSpecificValue method.

Thanks,

Rahul