Hi Paul,<br><br>my plain grok sandbox uses HTTP Basic Auth authentication. The credentials are sent alongside with the headers. As far as I know there's no way to logout from the session when using BasicAuth except starting a new Browser session. So I wonder if the zope session cookie you mentioned has anything to do with the authentication mechanism for the manager principal?!<br>
<br>Best wishes,<br>Michael.<br><br>
<br><div class="gmail_quote">On Sun, Aug 7, 2011 at 08:20, paul <span dir="ltr"><<a href="mailto:paul@aptrackers.com" target="_blank">paul@aptrackers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was wondering whether there's an easier way to do this.<br>
<br>
Currently, whenever I use the grok UI manager interface, my grok instance remains logged in as manager- so my app PAU instance detects a valid login and doesn't allow me to log out. I can log out my own users at application level, but since the 'manager' identity is not managed by my own PAU instance, I cannot seem to log out manager.<br>
<br>
Currently, I clear the zope session cookie, close the browser tab, and reload the URL to clear the login. I'm sure there's an easier way, but after much searching through the web online docs and the zope implementation code, I'm blowed if I know what it is.<br>
<br>
Can someone point me in the right direction?<br>
<br>
<br>_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org" target="_blank">Grok-dev@zope.org</a><br>
<a href="https://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">https://mail.zope.org/mailman/listinfo/grok-dev</a><br>
<br></blockquote></div><br>