Grouper Users - Open Discussion List

[Chris Hyzer <>]

I put that in my grouper-ui.properties and it worked fine (changed to email attribute).  (see below).  Is the ID of your source “jdbc”?  maybe not since it is an ldap source?  J

 

(grouper-ui.base.properties)

 

grouperUi.screenLabel2.sourceId.0 = jdbc

grouperUi.screenLabel2.screenEl.0 = ${subject.name}

 

 

(grouper-ui.properties)

 

grouperUi.screenLabel2.screenEl.0 = ${subject.getAttributeValue('email')}

 

If that’s not the problem send us a sanitized copy of your sources.xml

 

Thanks,

Chris

 

 

 

From: [mailto:] On Behalf Of Rob Gorrell
Sent: Wednesday, October 01, 2014 10:05 AM
To: Chris Hyzer
Cc:
Subject: Re: [grouper-users] UI displaying group members as empty checkboxes

 

Ok, I see where you are talking about... so I added the following override to my grouper-ui.properties:
grouperUi.screenLabel2.screenEl.0 = ${subject.getAttributeValue('lfNameUsername')}

"lfNameUsername" is a virtual attribute i've defined for my LDAP people in sources.xml to create "lname, fname (username)" display of subjects.

However, this still doesn't display in the 2.2 UI... the 2.2 UI still seems to be using subject.name for its listings. I even tried going into grouper-ui.base.properties and updating the default line, replacing ${subject.name} with ${subject.getAttributeValue('lfNameUsername')} and still its displaying name. Am I not allowed to use virtual attributes as a value here?

-Rob

 

On Tue, Sep 30, 2014 at 4:18 PM, Chris Hyzer <> wrote:

See this section of grouper-ui.properties, just edit the jdbc one or add another.  Let me know if it worked for you

 

# this configures  how subjects look in the UI v2.2.  This is the short version of the subject

grouperUi.screenLabel2.sourceId.0 = jdbc

grouperUi.screenLabel2.screenEl.0 = ${subject.name}

 

grouperUi.screenLabel2.sourceId.1 = g:gsa

grouperUi.screenLabel2.screenEl.1 = ${subject.getAttributeValue('displayExtension')}

 

grouperUi.screenLabel2.sourceId.2 = g:rsa

grouperUi.screenLabel2.screenEl.2 = ${subject.getAttributeValue('displayExtension')}

 

grouperUi.screenLabel2.sourceId.3 = grouperEntities

grouperUi.screenLabel2.screenEl.3 = ${subject.getAttributeValue('displayExtension')}

 

thanks,

Chris

 

From: Rob Gorrell [mailto:]
Sent: Tuesday, September 30, 2014 4:12 PM
To: Chris Hyzer
Cc:
Subject: Re: [grouper-users] UI displaying group members as empty checkboxes

 

Sorry to keep dredging up an old thread, but I wanna ask how these settings work against the new 2.2 UI?

Based on the original advice, I had modified media.properties subject.display.default=description to subject.display.default=lfNameUsername to get my lists of subjects to display the way i wanted them... that was in version 2.1.3.

Now with 2.2.0, i found the same setting in grouper-ui.base.properties and used grouper-ui.properties to override per the new configuration model. This seems to have put things back to how i expect in the admin UI, but the V2 UI seems to ignore this setting and still show description. 

What is the correct setting to go after so the new V2 UI displays lists of subjects in the same manor as the original UI?

Thanks
-Rob

 

On Fri, May 24, 2013 at 11:01 AM, Chris Hyzer <> wrote:

I think it might be subject name or description.  You might be able to change this in the media.properties

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Rob Gorrell
Sent: Friday, May 24, 2013 10:45 AM
To:
Subject: [grouper-users] UI displaying group members as empty checkboxes

 

So I have created my first group, etc:sysadmingroup and placed 4 subjects into it. I did this all through the addSubject and addMember gsh commands. The group functions fine and grants me admin access, but I was noticing when I look at the membership list in the UI, I get four "<checkbox> is a direct member"... but it isn't showing the subjectId or name I had given to my subjects. I would guess the UI is displaying some attribute I have yet to defined for my subjects? can someone explain what attribute this would be and how I go about defining it for the 4 subjects i've hand created?

Thanks,
-Rob


--

Robert W. Gorrell
Middleware Engineer, Identity and Access Management

University of NC at Greensboro
336-334-5954

--

Robert W. Gorrell
Systems Architect, Identity and Access Management

University of NC at Greensboro
336-334-5954
PGP Key ID B36DB0CA

--

Robert W. Gorrell
Systems Architect, Identity and Access Management

University of NC at Greensboro
336-334-5954
PGP Key ID B36DB0CA