Grouper Users - Open Discussion List

At 1:50 PM -0500 6/7/07, Tom Barton wrote:
>  wrote:
> > We're now thinking of trying Tom's idea -- create a table within 
> > oracle with one user per row, and use that as a source instead of 
> > ldap. That should get rid of -- literally -- hundreds of thousands 
> > of ldap queries...
> >
> > So, what do I need to do?
> >
> > 1) can I just build the oracle table (including as columns all the 
> > attributes that Grouper will retrieve, including the "key" value 
> > for each person), edit the sources.xml to replace the ldap source 
> > with this new table? And run ldappc again? I would build the oracle 
> > table by exporting an ldif from the existing ldap server, and then 
> > loading that data into oracle.
>
> Yes.
>
> > 3) what can I get away with (minimally) as columns in the oracle 
> > table? I currently have this in my sources.xml file:
> >
> >     ///Attributes you would like to display when doing a search
> >      <attribute>uid</attribute>
> >      <attribute>cn</attribute>
> >      <attribute>department</attribute>
> >        <attribute>brownBRUID</attribute>
>
> Since these are precisely the attributes that constitute your 
> JNDI-based Subjects, they are the perfect set to constitute the same 
> Subjects obtained from a JDBC source. But the minimally necessary 
> set is the key, ie, what you identify as the subject's Id, and any 
> other uniquely identifying attributes needed for ldappc to be able 
> to find the ldap entry corresponding to a Subject (uid in your case).

would someone be willing to share a sources.xml file that was using 
an SQL/Oracle source for "people"? As opposed to where the group 
definitions are stored?