Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-226

subject attributes not handled consistently

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.4.2
    • 1.4.1
    • WS
    • None

    Description

      Hi Chris,

      Either I don't get it, or the example source is broken?
      For testing I use the example mysql source that is part of the quickstart installation. As far as I understand the example source contains 3 source- specific attributes: "loginid, name and description", specified bij the 'name'
      column in the subjectattribute table.

      sources.xml refers to these columns as lfname, loginid and descrtiption.
      According to the source.xml explanation
      (https://wiki.internet2.edu/confluence/display/i2miCommon/subject-0.3.1-doc)
      "Each row corresponds to exactly one subject, and the column names of the returned table are used as the attribute names of the subject objects created for each row".

      If I specify 'description' as an attribute I want returned by e.g.
      getGroupsLite (as attributes supplied in the wsSubject section of the answer) either in grouper-ws.properties or in the request (by specifying the
      subjectAttributeNames) I just don't get that attribute returned:

      <ns:wsSubject type="edu.internet2.middleware.grouper.ws.soap.WsSubject">
      <ns:attributeValues xsi:nil="true"/>
      <ns:id>mrvanes</ns:id>
      <ns:identifierLookup xsi:nil="true"/>
      <ns:name xsi:nil="true"/>
      <ns:resultCode>SUCCESS</ns:resultCode>
      <ns:sourceId>example</ns:sourceId>
      <ns:success>T</ns:success>
      </ns:wsSubject>

      What am I missing?

      Also, in sources.xml three param-names are referenced that I can't find back in the documentation: SubjectID_AttributeType, Name_AttributeType and Description_AttributeType. What are they? Generic parameters, or specific methods that belong to the example connector (and thus explained by reading the subject api sources?)

      Regards,
      Martin

      On Thursday 12 February 2009 16:04:42 Chris Hyzer wrote:
      > OK, here is how it works:
      >
      > 1. The default attribute names (comma separated) sent back for each
      > request are specified in grouper-ws.properties under the key:
      >
      > ws.subject.result.attribute.names
      >
      > 2. If the caller sets T to retrieve subject detail, then the
      > attributes will be appended to that list in grouper-ws.properties key:
      > ws.subject.result.detail.attribute.names
      >
      > 3. If the caller specifies subjectAttributeNames (comma separated),
      > then those will be appended to the list (independent of the detail attributes).
      >
      > So there are central settings, and caller settings that you need to
      > design for and specify...
      >
      > Make sense?
      >
      > I updated this doc:
      >
      >
      >https://wiki.internet2.edu/confluence/display/GrouperWG/Grouper+Web+Ser
      >vice
      >s
      >
      > Thanks,
      > Chris
      >
      > > ----Original Message----
      > > Sent: Thursday, February 12, 2009 4:20 AM
      > > To: Grouper Users Mailing List
      > > Subject: [grouper-users] Subject external attributes retrieval
      > >
      > > Hi,
      > >
      > > I was wondering if Grouper can assist in arbitrary subject
      > > attributes retrieval.
      > > Is it possible to return external subject attributes while
      > > retrieving subjects with includeSubjectDetail=true e.g? Or would
      > > this require 2 actions on the client side: one to retrieve a unique
      > > lookup key and source from grouper for the subject another to get
      > > the attributes in the external source?
      > >
      > > Regards,
      > > Martin

      Attachments

        Activity

          People

            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: