Tickets :: [#7270] OAuth support in the Horde API

Summary	OAuth support in the Horde API
Queue	Horde Base
Queue Version	Git master
Type	Enhancement
State	Accepted
Priority	1. Low
Owners	chuck (at) horde (dot) org
Requester	chuck (at) horde (dot) org
Created	08/31/2008 (6100 days ago)
Due
Updated	09/17/2010 (5353 days ago)
Assigned
Resolved
Milestone
Patch	No

09/17/2010 03:39:05 AM	Chuck Hagenbuch	Comment #2 Assigned to Chuck Hagenbuch Version ⇒ Git master	Reply to this comment
Some things to keep in mind when implementing this: http://arstechnica.com/security/guides/2010/09/twitter-a-case-study-on-how-to-do-oauth-wrong.ars http://oneforty.com/devblog/twitter-permissions-security/

08/31/2008 05:02:11 AM	Chuck Hagenbuch	Comment #1 State ⇒ Accepted Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ OAuth support in the Horde API Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No	Reply to this comment
Users should be able to grant access to their data on a per-application basis (perhaps even per-share, but that might be a bit much) through OAuth provider support. Our permissions system should be flexible enough to easily respect these grants when API calls are made (probably by taking the OAuth token and logging the user in with restricted permissions), allowing users to give other applications access to their Horde data without giving out their username and password.