Grouper Users - Open Discussion List

["Michael R. Gettes" <>]

I'd add a word of caution to this advice Tom.  For sites with Directory
entries containing "reasonable amounts of data" this could be a  
significant
performance problem.  If ldappc is accessing the directory with a  
priv'd identity
allowing access to all attributes and you are a site that stores  
pictures
in the directory - then you will get back huge amounts of data where  
it is
not required.  I would advise each site to consider its own  
environment and
their performance needs and gauge for themselves whether or not they  
should
specify the <atttribute> elements.  While it will be "easiest" to simply
remove these elements - it is usually wiser to include them and only  
specify
the attributes really needed for best performance and an  
understanding of how
and why things work.

/mrg

On May 30, 2007, at 11:42, Tom Barton wrote:

> > 3) edit sources.xml
> > At the bottom of the file:
> >      ///Attributes you would like to display when doing a search
> >      <attribute>uid</attribute>
> >      <attribute>cn</attribute>
> >      <attribute>department</attribute>
> >        <attribute>brownBRUID</attribute>
> > add an attribute element referring to the key value that links  
> > your grouper DB to ldap person objects (in our case, this is  
> > brownBRUID )
>
> Note that <attribute> elements are only used by the  
> JNDISourceAdapter. If any are present, only the listed attributes  
> are returned in LDAP queries initiated by JNDISourceAdapter. If  
> none are present, all attributes are returned in the LDAP query. So  
> you can also just remove all <attribute> elements from sources.xml.