Grouper Users - Open Discussion List

["GW Brown, Information Systems and Computing" <>]

Hi Chuck,

How you 'logout' depends on your authentication scheme. The QuickStart 
depends on basic HTTP Authentication, unless you set it up otherwise. There 
is no guaranteed way, from the application side, of forcing a web client to 
'forget' a previous authentication. This is the reason why there is no 
Logout link by default. We can kill the Java HttpSession, but the client 
will still be authenticated. The only safe way of logging out is to close 
all your browser windows (Mozilla in particular since it shares state 
between windows).

If you want to logout, but then re-login as the same user, there is an 
action '/grouper/logout.do' which kills the HttpSession, and should behave 
as you want.

I don't know anything about Empirix, but I would look to see if you have 
control over the internal HTTP client they must be using, to clear HTTP 
authentication (Firefox allows you to do this), or if you can 'destroy' the 
current client and create a new one which does not have any 'history'.

If you are using a different authentication scheme, you must kill the 
Grouper UI HttpSession AND logout of your authentication scheme, or at 
least  force a re-authentication. You can achieve this by overriding the 
struts-config action:
<action path="/logout" scope="request"
       type="edu.internet2.middleware.grouper.ui.actions.LogoutAction"
       unknown="false"
       validate="false">
   </action>

to include
        <forward name="Index" path="<Your Logout URL>" redirect="true"/>

Whether a logout link appears in the UI is controlled by the 
media.properties key 'logout.link.show'. If it is set to 'true' a link will 
appear. You can set this in build.properties and the build will modify 
media.properties for you.

Regards,

Gary

--On 11 October 2006 15:11 -0500 Chuck Miller 
<> wrote:

> I am testing the Grouper UI using Empirix.  I would like to know how to
> log out of the UI because I need to log back into the UI in order to
> write additional tests.
>
>
>
> Any suggestions?
>
>
>
> Thanks,
>
> Chuck



----------------------
GW Brown, Information Systems and Computing