Grouper Users - Open Discussion List

[Chris Hyzer <>]

The location match will fix if the user goes directly to a deep link passed 
that location and you want the user to be forced to authenticate.  If you are 
authenticated in the Grouper UI, and you click to the lite UI, then that is 
not the problem.  Can you send me the version number of grouper and send me 
another copy of the stack?  Also, if you know where the username is, that 
would be helpful.  Is that in request.getRemoteUser()?

Thanks,
Chris

-----Original Message-----
From: Scott Koranda 
[mailto:]
 
Sent: Thursday, April 22, 2010 2:50 PM
To: 

Subject: [grouper-users] more on Lite UI Authentication

Hi,

Please see this thread:

https://archives.internet2.edu/wws/arc/grouper-users/2010-02/msg00007.html

Was this ever resolved? I am facing the exact same situation.

My httpd configuration looks like this:

        <Location /grouper>
                AuthType shibboleth
                ShibRequestSetting requireSession 1
                Require user ~ 
^.+@LIGO.ORG$
        </Location>

        <Location /grouper-ws>
                AuthType shibboleth
                ShibRequestSetting requireSession 1
                Require user ~ 
^.+@LIGO.ORG$
        </Location>

        ProxyPass /grouper/ ajp://127.0.0.1:8009/grouper/
        ProxyPass /grouper-ws/ ajp://127.0.0.1:8009/grouper-ws/

This works well for the standard UI and for Grouper WS, but if
I click on "Manage members lite" in the standard UI and
attempt to use the lite UI then I get same stack trace as
mentioned in that thread.

Before I try using <LocationMatch > instead of <Location> I
would like to understand the requirement of the lite UI so
that I know precisely what needs to be exposed/authenticated.

Thanks,

Scott