Grouper Users - Open Discussion List

[Julio Polo <>]

Sure :-)

-julio

On Wed, Oct 21, 2015 at 2:38 AM, Chris Hyzer <> wrote:

I think the correct behavior is to append to the default set like 2.2 does.  Is that ok?  J

 

From: [mailto:] On Behalf Of Julio Polo
Sent: Friday, September 25, 2015 4:20 PM
To:
Subject: [grouper-users] ws.subject.result.detail.attribute.names vs. requested subjectAttributeNames

 

When my WS request specifies the subjectAttributeNames and sets includeSubjectDetail to true as done here:

<WsRestGetMembersRequest>
  <wsGroupLookups>
   <WsGroupLookup>
    <groupName>some:group:here</groupName>
   </WsGroupLookup>
  </wsGroupLookups>

  <includeSubjectDetail>T</includeSubjectDetail>
  <subjectAttributeNames>
    <string>uid</string>
  </subjectAttributeNames>

  <memberFilter>all</memberFilter>
 </WsRestGetMembersRequest>,

is the response supposed to include just the attributes I specified in the request or is it supposed to also include the attributes specified in grouper-ws.base.properties:

# subject result attribute names when extended data is requested (comma separated)
# default is name, description
# note, these will be in addition to ws.subject.result.attribute.names
ws.subject.result.detail.attribute.names =

I noticed a change in behavior from 2.1.5 to 2.2.1.  When includeSubjectDetails is true as in the above request, the 2.1 response only includes the uid I specified in the request, whereas the 2.2 response includes the uid, name, and description.  Which is the correct behavior?

Julio Polo
Enterprise Middleware, Identity and Access Management
Information Technology Services
University of Hawaii