Grouper Users - Open Discussion List

[Chris Hyzer <>]

To add a little more info... each of the 3 queries is used if different 
circumstances... but yes, the attributes returned should be consistent.  If 
grouper knows the ID of the subject, and wants to look it up, there is a 
query for that.  If you are searching in the search box in the UI, there is a 
query for that.  Etc.

One gray area I have is if you map a col to the description field of the 
Subject, then is that available by the label "description" in the web 
service?  Right now the answer is no, so the easiest thing is to have a 
"description" col or alias returned, and just map that to the description 
field of Subject, and not worry about it...

Regards,
Chris

> -----Original Message-----
> From: Tom Barton 
> [mailto:]
> Sent: Wednesday, February 18, 2009 2:29 PM
> To: Martin van Es
> Cc: Grouper Users Mailing List
> Subject: Re: [grouper-users] Subject external attributes retrieval
> 
> Martin van Es wrote:
> > I still have a question about the foreign attributes: what is it that
> makes
> > them 'tick'?
> > I understand from the documentation that any column returned
> translates to an
> > available attribute. So if I would use a (hypothetical) query 'select
> foo as
> > bar from test where id=?' I would automagically have an attribute
> 'bar'
> > available in my grouper queries? If this is true, which query is
> responsibale
> > for this magic? I see 3 in sources.xml for the example source:
> searchSubject,
> > searchSubjectByIdentifier and search.
> 
> That is true, and each of the 3 select statements configured for a JDBC
> source in sources.xml is responsible for presenting Subject attributes
> from the back-end source. It's best and simplest for all three select
> statements to return the same set of columns from the back-end, though
> it's not strictly necessary.
> 
> For the JNDISourceAdapter, the set of 'attribute' elements defines the
> attributes returned by all 3 LDAP queries.
> 
> Tom