Tickets :: [#12766] Horde_IMAP: Should not require password for XOAUTH2

6.0.0-beta1

11/8/25

Summary	Horde_IMAP: Should not require password for XOAUTH2
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	stuart (at) contatta (dot) com
Created	10/15/2013 (4407 days ago)
Due
Updated	10/15/2013 (4407 days ago)
Assigned
Resolved	10/15/2013 (4407 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/15/2013 10:59:49 PM	Michael Slusarz	Comment #4	Reply to this comment
Fair enough ? do you have an anticipated release date for Horde_Imap 3.0? I'd like to finish it so that IMP 6.2 can use it. So that would be by the end of the year.

10/15/2013 10:57:00 PM	stuart (at) contatta (dot) com	Comment #3	Reply to this comment
Fair enough ? do you have an anticipated release date for Horde_Imap 3.0? Cheers

10/15/2013 10:01:03 PM	Michael Slusarz	Comment #2 Assigned to Michael Slusarz State ⇒ Resolved	Reply to this comment
This has already been changed for Horde_Imap_Client 3. From UPGRADING: The 'xoauth2_token' has been removed. Instead, an object that implements the Horde_Imap_Client_Xoauth2 class should be passed into the 'password' option. A 'password' option has been required for all of Horde_Imap_Client 2. I don't see a need to change that for now (XOAUTH2 was a recent "add-on" addition). It's not that big of a deal to simply pass in a bogus password for now.

10/15/2013 07:43:34 PM	stuart (at) contatta (dot) com	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Summary ⇒ Horde_IMAP: Should not require password for XOAUTH2 Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
When specifying an xoauth2_token, password should not be required when constructing Horde_Imap_Client_Socket