Tickets :: [#9261] Some login tasks need "real" authentication

6.0.0-alpha14

7/3/25

Summary	Some login tasks need "real" authentication
Queue	Horde Base
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	09/20/2010 (5400 days ago)
Due
Updated	10/11/2010 (5379 days ago)
Assigned	10/07/2010 (5383 days ago)
Resolved	10/11/2010 (5379 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/11/2010 10:16:10 AM	Jan Schneider	Comment #4 State ⇒ Resolved	Reply to this comment
Looks good.

10/07/2010 06:48:00 AM	Michael Slusarz	Comment #3 State ⇒ Feedback	Reply to this comment
How about this? As mentioned in the commit, we don't have a CLI interface for entering auth credentials but at least it now provides a warning and doesn't throw PHP errors (at least in my tests).

10/07/2010 06:45:56 AM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git for this ticket: ~~Bug #9261~~: Allow SystemTasks to be skipped If a system task requires auth, skip it until the user is authenticated. For bin/run_task, if a task is skipped output a warning message. Currently, no UI exists for allowing authentication from the command line. create mode 100644 imp/lib/LoginTasks/SystemTask/UpgradeFromImp4Auth.php http://git.horde.org/diff.php/framework/LoginTasks/lib/Horde/LoginTasks/SystemTask.php?rt=horde-git&r1=4a429dc92a41ef04960575f7032669fe7b3e997f&r2=95695d805d9824a0fb7ef63e539bf156bc5bf680 http://git.horde.org/diff.php/framework/LoginTasks/lib/Horde/LoginTasks/Tasklist.php?rt=horde-git&r1=f385719d99b4dfe66097686a4aeba432a110b6e8&r2=95695d805d9824a0fb7ef63e539bf156bc5bf680 http://git.horde.org/diff.php/framework/LoginTasks/package.xml?rt=horde-git&r1=3224e2ac4b092b0315e8655b61aab86f6372b420&r2=95695d805d9824a0fb7ef63e539bf156bc5bf680 http://git.horde.org/diff.php/horde/bin/run_task?rt=horde-git&r1=b13cd375d8832bf7ae7ed16fe587476e7d4cd214&r2=95695d805d9824a0fb7ef63e539bf156bc5bf680 http://git.horde.org/diff.php/imp/lib/LoginTasks/SystemTask/UpgradeFromImp4.php?rt=horde-git&r1=1121fb4fdde21774156cca072cbce4f6aac49313&r2=95695d805d9824a0fb7ef63e539bf156bc5bf680 http://git.horde.org/co.php/imp/lib/LoginTasks/SystemTask/UpgradeFromImp4Auth.php?rt=horde-git&r=95695d805d9824a0fb7ef63e539bf156bc5bf680

09/20/2010 12:08:12 PM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Assigned to Michael Slusarz Summary ⇒ Some login tasks need "real" authentication Type ⇒ Bug State ⇒ Assigned Queue ⇒ Horde Base	Reply to this comment
Some login tasks, for example the Upgrade task in IMP, require "real" authentication at the application backend. bin/run_tasks only calls setAuth() though, so such tasks fail with cryptic error messages. We could add some property to Horde_LoginTasks_Task that determines whether the task could be run through bin/run_task. But maybe there is a some way to check the authentication layer whether a user is "really" logged in, and call that in the task classes that need it?