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

grouper-ws.base.properties / ws.client.user.group.name no longer commented

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.4.0
    • 2.4.0.patch, 2.5.0, 2.4.1
    • WS
    • None

    Description

      commit master 148a6ab441db6 2018-08-06 09:33:47

      {{grouper-ws/grouper-ws/conf/grouper-ws.base.properties

      1. If there is an entry here for group name, then all web service client users must be in this group (before the actAs)
        -#ws.client.user.group.name = etc:webServiceClientUsers
        +ws.client.user.group.name = etc:webServiceClientUsers
        }}

      Was this intended? After upgrading to 2.4, our clients can no longer access WS. We had never set ws.client.user.group.name, thus allowing all users access. Now it is expecting users to be in group etc:webServiceClientUsers (which doesn't exist in our setup).

      It may be a good idea anyway to add a whitelist group, so we may try this as a workaround. I will also try overriding with ws.client.user.group.name = <blank>, but it's possible it won't work if blank values are ignored.

      Attachments

        Activity

          People

            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            chad.redman@at.internet2.edu Chad Redman (unc.edu)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Smart Checklist