[Tickets #8475] Re: Skipping login tasks not working as expected

bugs at horde.org bugs at horde.org
Wed Aug 19 18:13:35 UTC 2009


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8475
------------------------------------------------------------------------------
  Ticket             | 8475
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Skipping login tasks not working as expected
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Jan Schneider, Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-08-19 14:13) wrote:

> Ah, I found the switch to trigger that behavior. I had hordeauth set  
> to false during debugging this. If I turn it on, I'm right logged in  
> to IMP. But without that I get the mentioned behavior, and not the  
> IMP login page.

Finally reproduced by removing myself from admin list.  When rewriting  
Horde_Registry::hasPermission(), I neglected the special case of a  
user not authenticated to an app but requesting only SHOW permission.   
In this single case, we need to do a permissions check since this is  
the only permission allowed if not authenticated.  See:

http://lists.horde.org/archives/commits/2009-August/001705.html

Still can't reproduce the rest though, no matter what combo of  
auth/admin/initial_app parameters I set.  At worst (a combo that  
doesn't auto login to IMP), the IMP portal block reports it is not  
authenticated and the IMP sidebar link doesn't show anything.   
Clicking on an IMP/Mail link leads to the login page.  All of this is  
working as expected.

I'm not sure how imp_imap->ob is not set in the garbage collection  
class.  To reach there, we have to successfully finish IMP  
authentication which by definition requires the Horde_Imap_Client  
object to be loaded into the session.  Might be useful to do a print_r  
on the imp_imap->ob object in IMP_Imap_Tree to see what it is set to.






More information about the bugs mailing list