Grouper Users - Open Discussion List

[Paul Engle <>]

For person subjects, you can set the display of the Members tab by
setting a pair of properties in the grouper-ui.properties file. I have
ours set with:

grouperUi.screenLabel2.sourceId.4 = rice
grouperUi.screenLabel2.screenEl.4 = ${subject.getAttributeValue('fullName')}

There are 3 source adapters baked in to the grouper-ui.base.properties
file, so I put mine at index 4. The first prop has the name of the
source adapter, and the second is whatever attribute you want to
display. It works with default attributes or custom attributes defined
in sources.xml (or subject.properties).

We also wanted to change the display of group subjects, but that process
doesn't work for groups. I ended up setting an override in
WEB-INF/clases/grouperText/grouper.text.en.us.properties for the
guiGroupShortLink property.

  -paul

On 11/13/2017 12:34 PM, Black, Carey M. wrote:
> Carl,
> 
>  
> 
> So that I can better understand your question, because I may have some
> of the same questions, could you answer a few questions about your
> question?   :)
> 
> Sorry for the HTML email. ( Screen shots embedded… Ugh. )
> 
>  
> 
>  
> 
> 1) Where exactly are you asking about in the UI?
> 
>                 I have been able to work out how to modify the "dynamic
> drop down list" (result of a partial value search) from the "type in a
> field and have 'auto completion' do a search" parts. (for LDAP sources)
> 
>                 But I have not figure out how to make the "Members" tab
> (on a group) show the expanded values that I want it to show there yet.
> 
>  
> 
>                 Example:
> 
>                                
> 
>                 Not sure how to fix the list…
> 
>                                
> 
>  
> 
>                 NOTE: ( black.123 ) is suffixed to the search results,
> but not in the Members table display.
> 
>                 I suspect that
> 
>                                 the “auto completion lists” are more a
> direct result from the Subject API being executed at run time.
> 
>                                 the “UI tables” come from some data
> stashed in the Grouper DB, but I have not dug in to try to find where it
> is, or how it is populated.
> 
>  
> 
>                 So your solution might involve more than one “thing to
> change” if you want both to be the same. ( But I am just guessing.)
> 
>  
> 
>  
> 
> 2) What variety of Subject API types are you using? ( Only LDAP, Only
> SQL , both?)
> 
>                 It is my understanding that each Subject source could be
> configured independently.
> 
>                 Which may be an advantage or a burden depending on what
> you want.
> 
>                 Example:
> 
>                                 LDAP#1 --> SN, Given Name  (
> Some_attribute [no idea what it does for multi-valued attributes?? ] )
> 
>                                 SQL#1  --> Given Name Last Name ( "From
> the DB" )
> 
>                                 LDAP#2 --> SN, Given Name  (
> Some_other_attribute [no idea what it does for multi-valued attributes?? ] )
> 
>  
> 
> -- 
> 
> Carey Matthew 
> 
> 
>  
> 
>  
> 
> -----Original Message-----
> From: 
> 
> [mailto:]
>  On Behalf Of Waldbieser, Carl
> Sent: Monday, November 13, 2017 12:30 PM
> To: Chris Hyzer 
> <>
> Cc: grouper-users 
> <>
> Subject: [grouper-users] Re: Grouper UI - set subject columns in all
> relevant search/membership lists
> 
>  
> 
> Chris,
> 
>  
> 
> I take it that I need to manipulate my `sources.xml` to make this happen?
> 
> Do I need to use the JDBCC2 source, or will the LdapSourceAdapter be
> able to do this, too?
> 
>  
> 
> Where I am getting hung up is that I'm not entirely sure what the
> structure of the source adapters is allowed to actually look like, and
> what stanzas will be translated into something meaningful.
> 
>  
> 
> Also, is this something I can test in the GSH somehow, or do I need to
> update a WAR file and restart a container to test each change?
> 
>  
> 
> Thanks,
> 
> Carl Waldbieser
> 
> ITS Systems Programmer
> 
> Lafayette College
> 
>  
> 
> ----- Original Message -----
> 
> From: "Chris Hyzer" 
> <
>  
> <mailto:>>
> 
> To: "waldbiec" 
> <
>  
> <mailto:>>,
> "grouper-users" 
> <
> <mailto:>>
> 
> Sent: Monday, November 13, 2017 11:47:58 AM
> 
> Subject: RE: Grouper UI - set subject columns in all relevant
> search/membership lists
> 
>  
> 
> I use jdbc2 source at Penn, here is a description
> 
>  
> 
> https://spaces.internet2.edu/display/Grouper/Penn+subject+source+JDBC2+example
> 
>  
> 
> thanks
> 
> Chris
> 
>  
> 
> -----Original Message-----
> 
> From: 
> 
> <mailto:>
> [mailto:]
>  On Behalf Of Waldbieser, Carl
> 
> Sent: Sunday, November 12, 2017 2:06 PM
> 
> To: grouper-users 
> <
> <mailto:>>
> 
> Subject: [grouper-users] Grouper UI - set subject columns in all
> relevant search/membership lists
> 
>  
> 
>  
> 
> What is the recommended way to add additional subject attribute columns
> to all the relevant search result and membership lists.
> 
>  
> 
> Currently, we are only showing the subject Identifier.  This shows up as
> "Entity name" on the membership list for a group or in the "Name" column
> for a search result.
> 
>  
> 
> I'd really like to show the first name, last name, and subject ID in the
> columns instead of just the subject ID.
> 
>  
> 
> In the detail widget for a subject, I can see these attributes, but I'd
> like to see them in the list views, too.
> 
>  
> 
> Thanks,
> 
> Carl Waldbieser
> 
> ITS Systems Programmer
> 
> Lafayette College
> 

-- 
Paul Engle
Office of Information Technology

713-348-4702